Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a48596567cdbeab589ed1c5a2951566f757df82686a341574c88a3ffcb1751

Tx prefix hash: 5bcd8b9a598d24ad819f72b6992aca08e5c6df55b8ce5faa29db5a9b35fed05d
Tx public key: b59b625cf5fd525f29d6e6e210e4e9e1db309c497d1078352ab2ea1cf5c39bc1
Timestamp: 1764652236 Timestamp [UCT]: 2025-12-02 05:10:36 Age [y:d:h:m:s]: 00:021:21:12:22
Block: 1424608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15660 RingCT/type: yes/0
Extra: 01b59b625cf5fd525f29d6e6e210e4e9e1db309c497d1078352ab2ea1cf5c39bc1021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b3f38628ed55b193970d23b71b177f0681de4bbe9130662533c52ed092f418e 0.600000000000 1913239 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": 1424618, "vin": [ { "gen": { "height": 1424608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b3f38628ed55b193970d23b71b177f0681de4bbe9130662533c52ed092f418e" } } ], "extra": [ 1, 181, 155, 98, 92, 245, 253, 82, 95, 41, 214, 230, 226, 16, 228, 233, 225, 219, 48, 156, 73, 125, 16, 120, 53, 42, 178, 234, 28, 245, 195, 155, 193, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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