Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e60aa1b07cd8489edac76b35df1fec9a747d25878baa44ab8b9b1e33ad1ea903

Tx prefix hash: 9609cd0ebe671afc370e23cd26714f484defe6522eb6558eaf3242a1ecc7c10e
Tx public key: 922212dfca841aee531f5e4ac1c2b67c05f084e6834dd25c0b58f521373b84a4
Timestamp: 1583932495 Timestamp [UCT]: 2020-03-11 13:14:55 Age [y:d:h:m:s]: 04:266:07:22:16
Block: 80474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085474 RingCT/type: yes/0
Extra: 01922212dfca841aee531f5e4ac1c2b67c05f084e6834dd25c0b58f521373b84a402110000002e3b1b9791000000000000000000

1 output(s) for total of 332.167410544000 dcy

stealth address amount amount idx
00: 3eb8d069d9cec6289a635432f9727d72aada1ff1d343fc21b69f916d706c7958 332.167410544000 147274 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": 80484, "vin": [ { "gen": { "height": 80474 } } ], "vout": [ { "amount": 332167410544, "target": { "key": "3eb8d069d9cec6289a635432f9727d72aada1ff1d343fc21b69f916d706c7958" } } ], "extra": [ 1, 146, 34, 18, 223, 202, 132, 26, 238, 83, 31, 94, 74, 193, 194, 182, 124, 5, 240, 132, 230, 131, 77, 210, 92, 11, 88, 245, 33, 55, 59, 132, 164, 2, 17, 0, 0, 0, 46, 59, 27, 151, 145, 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