Inscription was successfully inscribed in Bitcoin but its detail couldn't be displayed on oridinals.com. Maybe an index issue.

[6789tc]

The Inscription Genesis transaction could be perfectly found in oridinals.com, however, when I click on the link to inscription detail it returns "Internal Server Error".

Inscription Genesis txn: https://ordinals.com/tx/df968aa38e86d4df52ce27687625009d32e2ac03840c2d6b883a0ae94e783f45

Inscription detail: (Internal Server Error)
https://ordinals.com/inscription/df968aa38e86d4df52ce27687625009d32e2ac03840c2d6b883a0ae94e783f45i0

Can someone help me understand how is that possible? Thanks.

[gmart7t2]

This issue was fixed in ord 0.5.2 last week by this PR: https://github.com/casey/ord/pull/1971

The index needs rebuilding after switching to ord 0.5.2.

You can see the inscription being spent as fee here: https://mempool.space/tx/4613a965822828c4ce6a11b7fc23aa656d797ebbdc64106c49cec140d018a108

The inscription is at offset 1000 in the last output. The last output is 3046 sats and the fee is 2046 sats, the the inscription ends up being at offset 0 in the fee of this tx.

Here's a trace of the locations of the sat from inscription to the current location:

   0 - 784510 - Sat Apr  8 08:30:05 2023 - df968aa38e86d4df52ce27687625009d32e2ac03840c2d6b883a0ae94e783f45:0:0 - bc1p8np6xap5w9r26gplt2c4zxuf39mggntxruven9u4fzcf0jpluztqg5wh6x
   1 - 784525 - Sat Apr  8 10:06:27 2023 - 886020c18521ae15b27114a3f7174c6b6ecdfe37f663fc9847180eea65ce87ef:0:0 - bc1p8np6xap5w9r26gplt2c4zxuf39mggntxruven9u4fzcf0jpluztqg5wh6x
   2 - 785665 - Sun Apr 16 08:09:41 2023 - 38b5e449d5257b5e0821fcdd527d09170ad9567a7d69093c1c708d101dff8d36:0:0 - bc1p8np6xap5w9r26gplt2c4zxuf39mggntxruven9u4fzcf0jpluztqg5wh6x
   3 - 785978 - Tue Apr 18 08:13:48 2023 - 88da555fe91780ae7d952a80c4e003e7b1383872f3514754b155afe7d6ef0e79:0:0 - bc1p8np6xap5w9r26gplt2c4zxuf39mggntxruven9u4fzcf0jpluztqg5wh6x
   4 - 786436 - Fri Apr 21 14:24:02 2023 - 2289ee13748dd48f4a51dda0a2ec4ed9180172f45343dc22fce504b0961ab2ea:0:0 - bc1p8np6xap5w9r26gplt2c4zxuf39mggntxruven9u4fzcf0jpluztqg5wh6x
   5 - 786562 - Sat Apr 22 10:06:34 2023 - b6659a45e828c97d3a64e8926edbd28158bfad238a280a6680317e82bc7da993:0:1000 - bc1p4hny4qlvwtxp9yy7ve03wp5qm7tk3j39kt8rfce742u927vjlvgs3vzkx6
   6 - 786565 - Sat Apr 22 10:23:18 2023 - ff284e86bdc2a1a4251646f1af6981b4fdea40c9472036bb701c4caa24947961:0:633016573 - 1KFHE7w8BhaENAswwryaoccDb6qcT6DbYY
   7 - 786761 - Sun Apr 23 20:04:09 2023 - 7c50c1d1c9288839289e078bbe82980c18e1865c717a0977bf62a34d1a1a0d70:0:5731311392 - 1GX28yLjVWux7ws4UQ9FB4MnLH4UKTPK2z
   8 - 786761 - Sun Apr 23 20:04:09 2023 - b9136846ae92b09abc9a4afac1d15ba50e3edec601a8acede59ea5318aa60cb9:12:129426938 - 3PLDFhzPydfSuEx2jPC6uQJgTK1oN4XzrZ

Here's https://github.com/gmart7t2/ord tracking the location of the inscription correctly:

$ ord inscriptions --id df968aa38e86d4df52ce27687625009d32e2ac03840c2d6b883a0ae94e783f45i0
{
  "number": 993299,
  "height": 784510,
  "timestamp": 1680967805,
  "inscription": "df968aa38e86d4df52ce27687625009d32e2ac03840c2d6b883a0ae94e783f45i0",
  "location": "b9136846ae92b09abc9a4afac1d15ba50e3edec601a8acede59ea5318aa60cb9:12:129426938",
  "address": "3PLDFhzPydfSuEx2jPC6uQJgTK1oN4XzrZ",
  "amount": 173916129,
  "content_type": "text/html;charset=utf-8"
}

[veryordinally]

Updated ord on ordinals.com to 0.5.2 and rebuilt index. https://ordinals.com/inscription/df968aa38e86d4df52ce27687625009d32e2ac03840c2d6b883a0ae94e783f45i0 no longer gives an internal server error.