Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa115febc578d6eeea372dfaab1933da541556b5e4dbd84235bfa926d8227a43

Tx prefix hash: e8c9e1587d4e97ef19452abcf42757006e77424da8c1970b8ded72cc37d6f412
Tx public key: 2b5e7dfdd6c207e6d4ab5c402ad4843b56d0532cb7dc9eaf4372bef931df130d
Timestamp: 1762587937 Timestamp [UCT]: 2025-11-08 07:45:37 Age [y:d:h:m:s]: 00:058:04:47:22
Block: 1407505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41670 RingCT/type: yes/0
Extra: 012b5e7dfdd6c207e6d4ab5c402ad4843b56d0532cb7dc9eaf4372bef931df130d0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8934cf84c6970629db202dda442f6b7e83722c64e6284287cac6678b6f4c47d 0.600000000000 1895926 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": 1407515, "vin": [ { "gen": { "height": 1407505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8934cf84c6970629db202dda442f6b7e83722c64e6284287cac6678b6f4c47d" } } ], "extra": [ 1, 43, 94, 125, 253, 214, 194, 7, 230, 212, 171, 92, 64, 42, 212, 132, 59, 86, 208, 83, 44, 183, 220, 158, 175, 67, 114, 190, 249, 49, 223, 19, 13, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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