Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8a265093721e67e4777ea47fd1b965acf7a0d17582d39f3a8f1b91f79429f70

Tx prefix hash: a9729c6e7f0ddcff523fff1fb5ac718c304a9ed017ff38e12bd4068b17db524f
Tx public key: 2ade35049362da532a3e194bf11b9f740bfc449701e43c0491150fee3b475562
Timestamp: 1762002763 Timestamp [UCT]: 2025-11-01 13:12:43 Age [y:d:h:m:s]: 00:066:23:00:15
Block: 1402685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47922 RingCT/type: yes/0
Extra: 012ade35049362da532a3e194bf11b9f740bfc449701e43c0491150fee3b4755620211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd733a80b482b676a089d0ec5f88e9e2c9ebd533f3c1ee4f414937abf51fca01 0.600000000000 1891004 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": 1402695, "vin": [ { "gen": { "height": 1402685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd733a80b482b676a089d0ec5f88e9e2c9ebd533f3c1ee4f414937abf51fca01" } } ], "extra": [ 1, 42, 222, 53, 4, 147, 98, 218, 83, 42, 62, 25, 75, 241, 27, 159, 116, 11, 252, 68, 151, 1, 228, 60, 4, 145, 21, 15, 238, 59, 71, 85, 98, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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