Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 168ea2507758c54d28ed724abdc8e42dbe6ab57d231599c70c00495146ff4129

Tx prefix hash: ad6fae84dfaea77a04b7ce0f20bc9ae61871c9590bbafb1090f1d14c9e29b419
Tx public key: a765df7ead1faa03c082610b91e75461a9aa7480cb69997e58d0ecf86cf0cedf
Timestamp: 1757108681 Timestamp [UCT]: 2025-09-05 21:44:41 Age [y:d:h:m:s]: 00:076:00:43:18
Block: 1362187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54343 RingCT/type: yes/0
Extra: 01a765df7ead1faa03c082610b91e75461a9aa7480cb69997e58d0ecf86cf0cedf02110000000cb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ceca84bbb9ca2f7e4594a04a2bf35da7fbf0bd61c21be74928eaa87f5d8a0433 0.600000000000 1850218 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": 1362197, "vin": [ { "gen": { "height": 1362187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ceca84bbb9ca2f7e4594a04a2bf35da7fbf0bd61c21be74928eaa87f5d8a0433" } } ], "extra": [ 1, 167, 101, 223, 126, 173, 31, 170, 3, 192, 130, 97, 11, 145, 231, 84, 97, 169, 170, 116, 128, 203, 105, 153, 126, 88, 208, 236, 248, 108, 240, 206, 223, 2, 17, 0, 0, 0, 12, 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