Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b1d06c5a8a918ce98092a3e009d78f277376d1fcd4bd4f59abcdcabe2dc8799

Tx prefix hash: 5913cb2475244a0a54fb410e799674163a34a1dbce678fd61cbc98ed7d42dccb
Tx public key: be591366e57b8ed22d5e987f27dc0b641458cd8c52418848387b957d39a441be
Timestamp: 1763035687 Timestamp [UCT]: 2025-11-13 12:08:07 Age [y:d:h:m:s]: 00:014:21:54:15
Block: 1411219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10676 RingCT/type: yes/0
Extra: 01be591366e57b8ed22d5e987f27dc0b641458cd8c52418848387b957d39a441be0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13a80e8c6a87b069aef7e44cb0a7d0742fc56adf9f57efd78fd034a42de01564 0.600000000000 1899678 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": 1411229, "vin": [ { "gen": { "height": 1411219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a80e8c6a87b069aef7e44cb0a7d0742fc56adf9f57efd78fd034a42de01564" } } ], "extra": [ 1, 190, 89, 19, 102, 229, 123, 142, 210, 45, 94, 152, 127, 39, 220, 11, 100, 20, 88, 205, 140, 82, 65, 136, 72, 56, 123, 149, 125, 57, 164, 65, 190, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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