Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd645c618179e3cde01c83b67446015195e4ffdc5fb1a4d89b72aa3fb39a581a

Tx prefix hash: c5cb016dce3b2c52c633e48b38b79c2a6b68d7ee2bf3d890bfc6286eb6e0007f
Tx public key: 548f29ab723f5e82af78c77eeee09436e63a34aa00e1208678cae73a09a39c47
Timestamp: 1765091792 Timestamp [UCT]: 2025-12-07 07:16:32 Age [y:d:h:m:s]: 00:000:21:27:22
Block: 1428253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643 RingCT/type: yes/0
Extra: 01548f29ab723f5e82af78c77eeee09436e63a34aa00e1208678cae73a09a39c4702110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdf1f00a64d3fbdecd7385db0f3de38210511c1d0dca2921b4400e6b2cb98943 0.600000000000 1916968 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": 1428263, "vin": [ { "gen": { "height": 1428253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdf1f00a64d3fbdecd7385db0f3de38210511c1d0dca2921b4400e6b2cb98943" } } ], "extra": [ 1, 84, 143, 41, 171, 114, 63, 94, 130, 175, 120, 199, 126, 238, 224, 148, 54, 230, 58, 52, 170, 0, 225, 32, 134, 120, 202, 231, 58, 9, 163, 156, 71, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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