Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e36c34fbf2eeae824f3839398a78a10f67e95c4dc8d755f521c7b23313d756f0

Tx prefix hash: ac06c383111c8b22e365e93d83d6a546a7d224e98345c8b7463d9ccfd4176809
Tx public key: ef79b2410cdea41ebf28b01396db56125792adcfaddfa5199edaad3d772f15a4
Timestamp: 1581642325 Timestamp [UCT]: 2020-02-14 01:05:25 Age [y:d:h:m:s]: 05:088:11:00:04
Block: 64584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1215997 RingCT/type: yes/0
Extra: 01ef79b2410cdea41ebf28b01396db56125792adcfaddfa5199edaad3d772f15a402110c698b7d00000000000000000000000000

1 output(s) for total of 374.979227050000 dcy

stealth address amount amount idx
00: a615e093f74a5efb9f7d38512393a8ea186ea0002e54e6a7deee245441d5ca5a 374.979227050000 119103 of 0

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": 64594, "vin": [ { "gen": { "height": 64584 } } ], "vout": [ { "amount": 374979227050, "target": { "key": "a615e093f74a5efb9f7d38512393a8ea186ea0002e54e6a7deee245441d5ca5a" } } ], "extra": [ 1, 239, 121, 178, 65, 12, 222, 164, 30, 191, 40, 176, 19, 150, 219, 86, 18, 87, 146, 173, 207, 173, 223, 165, 25, 158, 218, 173, 61, 119, 47, 21, 164, 2, 17, 12, 105, 139, 125, 0, 0, 0, 0, 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