Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0dd147e3df2babc6755420e4c4331ce6aa6871b9dc0ecd59887c8af018530a6

Tx prefix hash: a8332bc5b25277260347ccd6a77bdb06cc367929f7e3169a928a060269e4c93e
Tx public key: 5d653f1f1c4f9b63868dcff246b8a4b1c09ce95086f58909d47971e131559c72
Timestamp: 1761055341 Timestamp [UCT]: 2025-10-21 14:02:21 Age [y:d:h:m:s]: 00:098:22:21:50
Block: 1394818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70646 RingCT/type: yes/0
Extra: 015d653f1f1c4f9b63868dcff246b8a4b1c09ce95086f58909d47971e131559c7202110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28f0c2959ba7b15ac3c9765ed45717bca079d6e16e24b3b39bea0f4ebed3b1e0 0.600000000000 1883093 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": 1394828, "vin": [ { "gen": { "height": 1394818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28f0c2959ba7b15ac3c9765ed45717bca079d6e16e24b3b39bea0f4ebed3b1e0" } } ], "extra": [ 1, 93, 101, 63, 31, 28, 79, 155, 99, 134, 141, 207, 242, 70, 184, 164, 177, 192, 156, 233, 80, 134, 245, 137, 9, 212, 121, 113, 225, 49, 85, 156, 114, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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