Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60a8e0ad7b468efa5d2eaeea0eebe078b05a62d67de7ba1c0ac2a968efa89f5c

Tx prefix hash: e62955842ee86ebe406e98a55214840016e50671fe404c48e9a528c5bb985175
Tx public key: b908f3d014ed727ea4631fc265d88275fb9f1f3486cf59166f5c82ee7ca8b5ed
Timestamp: 1717737791 Timestamp [UCT]: 2024-06-07 05:23:11 Age [y:d:h:m:s]: 00:282:04:26:50
Block: 1038805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201668 RingCT/type: yes/0
Extra: 01b908f3d014ed727ea4631fc265d88275fb9f1f3486cf59166f5c82ee7ca8b5ed0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5143bd3d126e20a4b7ed9a584e8260f1334dd03386fa011a9999355f803be674 0.600000000000 1507366 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": 1038815, "vin": [ { "gen": { "height": 1038805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5143bd3d126e20a4b7ed9a584e8260f1334dd03386fa011a9999355f803be674" } } ], "extra": [ 1, 185, 8, 243, 208, 20, 237, 114, 126, 164, 99, 31, 194, 101, 216, 130, 117, 251, 159, 31, 52, 134, 207, 89, 22, 111, 92, 130, 238, 124, 168, 181, 237, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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