Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21b6d99bc1f4bd9ef7eb8a54eb84eda669c235f6482bd26a4122c3bc37a0a5ca

Tx prefix hash: 2a98e50543d8dfbb885612fed32c54b5d45bab7091f49a8aed702f7769d602cd
Tx public key: 698fc67a836c00b1791ac60f6e522b5aee6de26deb33832dd86bbadfba6c0b08
Timestamp: 1574708372 Timestamp [UCT]: 2019-11-25 18:59:32 Age [y:d:h:m:s]: 05:362:08:45:46
Block: 17349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1399334 RingCT/type: yes/0
Extra: 01698fc67a836c00b1791ac60f6e522b5aee6de26deb33832dd86bbadfba6c0b0802110000000280094f5e000000000000000000

1 output(s) for total of 537.670788225000 dcy

stealth address amount amount idx
00: 08a9e79b1242c30876d34c78b6587e548fb6d30e1fbfcf04b316c18f772e5d19 537.670788225000 25101 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": 17359, "vin": [ { "gen": { "height": 17349 } } ], "vout": [ { "amount": 537670788225, "target": { "key": "08a9e79b1242c30876d34c78b6587e548fb6d30e1fbfcf04b316c18f772e5d19" } } ], "extra": [ 1, 105, 143, 198, 122, 131, 108, 0, 177, 121, 26, 198, 15, 110, 82, 43, 90, 238, 109, 226, 109, 235, 51, 131, 45, 216, 107, 186, 223, 186, 108, 11, 8, 2, 17, 0, 0, 0, 2, 128, 9, 79, 94, 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