Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2db45e9b16b1b1c72d681cec82362f419e688fdc52f8bb5ad631908281594083

Tx prefix hash: 96c4fbf2d82a3b1d242a44151eea80db82b3494173200589d662a03590f09e64
Tx public key: 9d7c6548fb1c97156c2bba59d9840e915ccf74f9a4c626490bf7d36d91619bb2
Timestamp: 1732576224 Timestamp [UCT]: 2024-11-25 23:10:24 Age [y:d:h:m:s]: 00:113:16:43:53
Block: 1161721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81077 RingCT/type: yes/0
Extra: 019d7c6548fb1c97156c2bba59d9840e915ccf74f9a4c626490bf7d36d91619bb2021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84277d6594ba0f5be42909fb7de3673f0ca03c0d366a65ea51a46002524ac368 0.600000000000 1647376 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": 1161731, "vin": [ { "gen": { "height": 1161721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84277d6594ba0f5be42909fb7de3673f0ca03c0d366a65ea51a46002524ac368" } } ], "extra": [ 1, 157, 124, 101, 72, 251, 28, 151, 21, 108, 43, 186, 89, 217, 132, 14, 145, 92, 207, 116, 249, 164, 198, 38, 73, 11, 247, 211, 109, 145, 97, 155, 178, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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