Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 543aef5789a3a8c7e4587d1d94a1d7c7cc6d94d15601edcce220fea4c3339508

Tx prefix hash: 483ddb4cac94eb8fc5577dd227897daba18161ff0251fc7f446f50dae74a71b0
Tx public key: 64a29efd6c7d6862a187535176b8fb2435a1a2ca007b79fa8dd9e8230955a3fb
Timestamp: 1755246931 Timestamp [UCT]: 2025-08-15 08:35:31 Age [y:d:h:m:s]: 00:051:10:26:01
Block: 1347109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36381 RingCT/type: yes/0
Extra: 0164a29efd6c7d6862a187535176b8fb2435a1a2ca007b79fa8dd9e8230955a3fb021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef8a82228f4a5dc4ecfaa059774ae8f77f62e5fb2d8a7d336851209b40177711 0.600000000000 1835022 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": 1347119, "vin": [ { "gen": { "height": 1347109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef8a82228f4a5dc4ecfaa059774ae8f77f62e5fb2d8a7d336851209b40177711" } } ], "extra": [ 1, 100, 162, 158, 253, 108, 125, 104, 98, 161, 135, 83, 81, 118, 184, 251, 36, 53, 161, 162, 202, 0, 123, 121, 250, 141, 217, 232, 35, 9, 85, 163, 251, 2, 17, 0, 0, 0, 4, 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