Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec8efd327a525e31022a4465046bd9cf3ebf44a5649b2d61989af43bf8bd6c81

Tx prefix hash: ffb5ca66b2d82e092063bb950eee800c150dc12cd413946a8a0ee5e32c1a446c
Tx public key: 71587887c2331a07800f238cd745a3fdf5b1aa6f4e9c2c32ca511f00e2b33ac2
Timestamp: 1762623529 Timestamp [UCT]: 2025-11-08 17:38:49 Age [y:d:h:m:s]: 00:044:21:56:09
Block: 1407800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32150 RingCT/type: yes/0
Extra: 0171587887c2331a07800f238cd745a3fdf5b1aa6f4e9c2c32ca511f00e2b33ac2021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c36e749164c3de04eda1d698341bab70b679d01b74ac1c9b89e20f4b7429924b 0.600000000000 1896221 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": 1407810, "vin": [ { "gen": { "height": 1407800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c36e749164c3de04eda1d698341bab70b679d01b74ac1c9b89e20f4b7429924b" } } ], "extra": [ 1, 113, 88, 120, 135, 194, 51, 26, 7, 128, 15, 35, 140, 215, 69, 163, 253, 245, 177, 170, 111, 78, 156, 44, 50, 202, 81, 31, 0, 226, 179, 58, 194, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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