Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 654b544df4d8710f5554ac6d77c378b0b3e5a10c2d8f0104cb183250aa2d9dff

Tx prefix hash: 5b97b39dcac2e2edbb703083e998eaa9d2ef5fac8ee98e7ee2ef360a3b1bee71
Tx public key: 8125d768ecd3203d87affba069d3838a3aad384fee8792cc91d3cdac80c2191e
Timestamp: 1713995963 Timestamp [UCT]: 2024-04-24 21:59:23 Age [y:d:h:m:s]: 01:199:03:27:51
Block: 1007782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400969 RingCT/type: yes/0
Extra: 018125d768ecd3203d87affba069d3838a3aad384fee8792cc91d3cdac80c2191e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 383bcdaa46e9659eb31db4c806af57f10c48d5eb846a1d0dfaf81e793c276b5d 0.600000000000 1469230 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": 1007792, "vin": [ { "gen": { "height": 1007782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "383bcdaa46e9659eb31db4c806af57f10c48d5eb846a1d0dfaf81e793c276b5d" } } ], "extra": [ 1, 129, 37, 215, 104, 236, 211, 32, 61, 135, 175, 251, 160, 105, 211, 131, 138, 58, 173, 56, 79, 238, 135, 146, 204, 145, 211, 205, 172, 128, 194, 25, 30, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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