Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 895e382a3dcb639a40ed3c827c74e2bfab7fe17a789bedd0c26873f30e01629d

Tx prefix hash: b3e3ea534c873cfe375733b1d25ee34f511b41234e50dd983814bef27b6d4804
Tx public key: 34cae2a18119526e4eef72f6feb19ca12424d7c3e10911c7801e3455c21fd7a9
Timestamp: 1762581636 Timestamp [UCT]: 2025-11-08 06:00:36 Age [y:d:h:m:s]: 00:085:08:15:56
Block: 1407451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60930 RingCT/type: yes/0
Extra: 0134cae2a18119526e4eef72f6feb19ca12424d7c3e10911c7801e3455c21fd7a9021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 811e51d9eb463c9048d686db171d5fc10a530c3198f8199ee97073fc40abd27d 0.600000000000 1895872 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": 1407461, "vin": [ { "gen": { "height": 1407451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "811e51d9eb463c9048d686db171d5fc10a530c3198f8199ee97073fc40abd27d" } } ], "extra": [ 1, 52, 202, 226, 161, 129, 25, 82, 110, 78, 239, 114, 246, 254, 177, 156, 161, 36, 36, 215, 195, 225, 9, 17, 199, 128, 30, 52, 85, 194, 31, 215, 169, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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