Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01d40d887c31462658aa10c54a225401e77045bd05b901e5f2f5c7e2da1fa2d

Tx prefix hash: 63401241056b8df5ad22e5083c7cf135f66015c35d644d5356e960fe40ce51a9
Tx public key: 2a7f7b55fd25dab6eb649025e8dda40c76df19a4f72dfe46e929f3c49f8edcb6
Timestamp: 1754914809 Timestamp [UCT]: 2025-08-11 12:20:09 Age [y:d:h:m:s]: 00:107:21:47:45
Block: 1344808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76374 RingCT/type: yes/0
Extra: 012a7f7b55fd25dab6eb649025e8dda40c76df19a4f72dfe46e929f3c49f8edcb6021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e720f2db6ab32316abca7fa56e7c2e02fc6c827654dd745ce097b658b5d172cd 0.600000000000 1832693 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": 1344818, "vin": [ { "gen": { "height": 1344808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e720f2db6ab32316abca7fa56e7c2e02fc6c827654dd745ce097b658b5d172cd" } } ], "extra": [ 1, 42, 127, 123, 85, 253, 37, 218, 182, 235, 100, 144, 37, 232, 221, 164, 12, 118, 223, 25, 164, 247, 45, 254, 70, 233, 41, 243, 196, 159, 142, 220, 182, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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