Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5493490d8c7795b3d536c9309239ea05faba5a5bc38fa97ba19bdf0b7f0f3552

Tx prefix hash: b38226b72dc2d5180b6d1d47a31a74b8d6b1c5cc8f9ede4f19c6196010acfffa
Tx public key: 70a1af2f4ff162dd11f17c7334de4b37d31466f48bfe12d54a361cf411659389
Timestamp: 1765190548 Timestamp [UCT]: 2025-12-08 10:42:28 Age [y:d:h:m:s]: 00:015:15:40:30
Block: 1429070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11199 RingCT/type: yes/0
Extra: 0170a1af2f4ff162dd11f17c7334de4b37d31466f48bfe12d54a361cf41165938902110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5474833091b1040e16f40463c5baa86d057d5a3d9d804eb8df9f4553e3b43207 0.600000000000 1917793 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": 1429080, "vin": [ { "gen": { "height": 1429070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5474833091b1040e16f40463c5baa86d057d5a3d9d804eb8df9f4553e3b43207" } } ], "extra": [ 1, 112, 161, 175, 47, 79, 241, 98, 221, 17, 241, 124, 115, 52, 222, 75, 55, 211, 20, 102, 244, 139, 254, 18, 213, 74, 54, 28, 244, 17, 101, 147, 137, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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