Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe02bf49b40e8c9f6e9bce42424768d3fd7c67774e240da73cf576620fa502a

Tx prefix hash: 9f5e96dd82370d0592138df5554d9c3515b10f3a3575f8290ea0c29ab9ac97d9
Tx public key: 24f2ab35ac7c2cc39d8bcaf5c9ec805183de2f6657923d18a3ff23d937b96a51
Timestamp: 1719003633 Timestamp [UCT]: 2024-06-21 21:00:33 Age [y:d:h:m:s]: 00:155:21:26:43
Block: 1049271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111589 RingCT/type: yes/0
Extra: 0124f2ab35ac7c2cc39d8bcaf5c9ec805183de2f6657923d18a3ff23d937b96a510211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0dd80eeef4aad248f697fa04df83c5fc522a8f57e2281168d31611d4d003c92 0.600000000000 1519370 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": 1049281, "vin": [ { "gen": { "height": 1049271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0dd80eeef4aad248f697fa04df83c5fc522a8f57e2281168d31611d4d003c92" } } ], "extra": [ 1, 36, 242, 171, 53, 172, 124, 44, 195, 157, 139, 202, 245, 201, 236, 128, 81, 131, 222, 47, 102, 87, 146, 61, 24, 163, 255, 35, 217, 55, 185, 106, 81, 2, 17, 0, 0, 0, 2, 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