Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 84cd89666c686539da1a9adf2fe01f1c5070c747f3345974f84a8ecbc6ad8284

Tx prefix hash: e05eccad904eae7c657d836bacb4d787757ffc910ca224353f57452e821d8519
Tx public key: 71c69b5be5286e1f5c52f550afe2f4b7297982de3a2c7bb9dcb0903eefb5d218
Timestamp: 1721027317 Timestamp [UCT]: 2024-07-15 07:08:37 Age [y:d:h:m:s]: 00:264:21:02:27
Block: 1066083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189219 RingCT/type: yes/0
Extra: 0171c69b5be5286e1f5c52f550afe2f4b7297982de3a2c7bb9dcb0903eefb5d21802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92b2f30f1dcfda838f88b4de060b781a6637b081c9471a721f3f553e734aa226 0.600000000000 1536654 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1066093, "vin": [ { "gen": { "height": 1066083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92b2f30f1dcfda838f88b4de060b781a6637b081c9471a721f3f553e734aa226" } } ], "extra": [ 1, 113, 198, 155, 91, 229, 40, 110, 31, 92, 82, 245, 80, 175, 226, 244, 183, 41, 121, 130, 222, 58, 44, 123, 185, 220, 176, 144, 62, 239, 181, 210, 24, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8