Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f64a975a6e572391729de46e3e49fe8b9c64ca4f089502d4e3620b39b51e839

Tx prefix hash: 8fda8354c9d66b29aeab6bdad8392dbcff6d9a66fe68968b4d258dace75b817d
Tx public key: defb88859b8bdd7ec96241b1c80f13496ceceb20c32097efa5463c058fc30901
Timestamp: 1757007670 Timestamp [UCT]: 2025-09-04 17:41:10 Age [y:d:h:m:s]: 00:121:01:59:04
Block: 1361328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86641 RingCT/type: yes/0
Extra: 01defb88859b8bdd7ec96241b1c80f13496ceceb20c32097efa5463c058fc30901021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47b6e2171a8d6b77c17704541aa8e946d614e204aaace3a5015ff9a8aecd3009 0.600000000000 1849341 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": 1361338, "vin": [ { "gen": { "height": 1361328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47b6e2171a8d6b77c17704541aa8e946d614e204aaace3a5015ff9a8aecd3009" } } ], "extra": [ 1, 222, 251, 136, 133, 155, 139, 221, 126, 201, 98, 65, 177, 200, 15, 19, 73, 108, 236, 235, 32, 195, 32, 151, 239, 165, 70, 60, 5, 143, 195, 9, 1, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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