Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e876e9fc32cead5339ee5943155d687d707c33f4449593a2dc09bf0ab907da3d

Tx prefix hash: 0dd4fe10f1ddb2b5652a6716e792c094e6b872bc231e5acfdf166b530ce59153
Tx public key: 216a3488e1adf519aae84ca94c935d6c15e76cfa464d3a27edc245524162ceb7
Timestamp: 1704846010 Timestamp [UCT]: 2024-01-10 00:20:10 Age [y:d:h:m:s]: 01:117:18:34:58
Block: 931908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345298 RingCT/type: yes/0
Extra: 01216a3488e1adf519aae84ca94c935d6c15e76cfa464d3a27edc245524162ceb702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5375691767c32868f8dc003c1d53cbbf0f7880c8925b10b87b3bb6febc2f4b3 0.600000000000 1389814 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": 931918, "vin": [ { "gen": { "height": 931908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5375691767c32868f8dc003c1d53cbbf0f7880c8925b10b87b3bb6febc2f4b3" } } ], "extra": [ 1, 33, 106, 52, 136, 225, 173, 245, 25, 170, 232, 76, 169, 76, 147, 93, 108, 21, 231, 108, 250, 70, 77, 58, 39, 237, 194, 69, 82, 65, 98, 206, 183, 2, 17, 0, 0, 0, 3, 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