Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 122aa18f438a02cc4cf317074b12121079c7fd811c31047907d2cc1b9b1f60eb

Tx prefix hash: 4842651ba543c32a8803f8c93222d448a8c32008a12e9cf9ef4be369109786b4
Tx public key: d168cb0eac2f68c465f159e9d652cd64cb9d82e36d6b370162f0aa5c53ee78dc
Timestamp: 1703998853 Timestamp [UCT]: 2023-12-31 05:00:53 Age [y:d:h:m:s]: 01:096:18:29:19
Block: 924884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330281 RingCT/type: yes/0
Extra: 01d168cb0eac2f68c465f159e9d652cd64cb9d82e36d6b370162f0aa5c53ee78dc0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76a5eaf44bd2a9fcb0285f90dae365c52f76237c7f5bd3fafa0c32ac43a102b2 0.600000000000 1382644 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": 924894, "vin": [ { "gen": { "height": 924884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76a5eaf44bd2a9fcb0285f90dae365c52f76237c7f5bd3fafa0c32ac43a102b2" } } ], "extra": [ 1, 209, 104, 203, 14, 172, 47, 104, 196, 101, 241, 89, 233, 214, 82, 205, 100, 203, 157, 130, 227, 109, 107, 55, 1, 98, 240, 170, 92, 83, 238, 120, 220, 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