Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b80eb206a4cf3ea51571744ac2e3d1f13e9507293bcb2d559465475e1bc1730

Tx prefix hash: 4e89f1bac701d176ba6f850425665bbe24945f17704967b4ad2254bca82ff984
Tx public key: b1443afbb4f53246e8bc74797d3ca63e74b2dd1717e0b7f9ff473cec45dc3c07
Timestamp: 1765054410 Timestamp [UCT]: 2025-12-06 20:53:30 Age [y:d:h:m:s]: 00:015:05:22:56
Block: 1427934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10915 RingCT/type: yes/0
Extra: 01b1443afbb4f53246e8bc74797d3ca63e74b2dd1717e0b7f9ff473cec45dc3c0702110000000dd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4b8a22d5ac926e080fa572b4f4e8e1ed08ec06acf672256351f4aea9bcaf270 0.600000000000 1916641 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": 1427944, "vin": [ { "gen": { "height": 1427934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4b8a22d5ac926e080fa572b4f4e8e1ed08ec06acf672256351f4aea9bcaf270" } } ], "extra": [ 1, 177, 68, 58, 251, 180, 245, 50, 70, 232, 188, 116, 121, 125, 60, 166, 62, 116, 178, 221, 23, 23, 224, 183, 249, 255, 71, 60, 236, 69, 220, 60, 7, 2, 17, 0, 0, 0, 13, 214, 225, 157, 124, 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