Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18206a3f907dd8de879e2d618d2fdeeb14371aeda666c9825efece15446f8155

Tx prefix hash: 159d0554b337abb1bc8af37b07c89c8102d1cdcb3d7e5c418e07e54820210724
Tx public key: def26dd51c6c220342e91a1ccb7e9a5549d175f8a4705b0eea2d8bbbdee7ef04
Timestamp: 1755206864 Timestamp [UCT]: 2025-08-14 21:27:44 Age [y:d:h:m:s]: 00:050:23:40:31
Block: 1346843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35994 RingCT/type: yes/0
Extra: 01def26dd51c6c220342e91a1ccb7e9a5549d175f8a4705b0eea2d8bbbdee7ef04021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c34f53e203956a3862ff55ace5d5a2c3290abd514f5f074ef2a08343a455d44 0.600000000000 1834752 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": 1346853, "vin": [ { "gen": { "height": 1346843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c34f53e203956a3862ff55ace5d5a2c3290abd514f5f074ef2a08343a455d44" } } ], "extra": [ 1, 222, 242, 109, 213, 28, 108, 34, 3, 66, 233, 26, 28, 203, 126, 154, 85, 73, 209, 117, 248, 164, 112, 91, 14, 234, 45, 139, 187, 222, 231, 239, 4, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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