Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd23ffaceb445b3435661ed30edd8651b72b0b5d7380db0a36be7f4f33af9000

Tx prefix hash: 00db161bb0e036f96774d1e8c0a358c219292c2b13068696352b85da68282dc5
Tx public key: 11ae885da268844717de01aa8e8d6aa9ba6fa21f27d3754cae10f0f92d08a0aa
Timestamp: 1736376153 Timestamp [UCT]: 2025-01-08 22:42:33 Age [y:d:h:m:s]: 00:069:12:23:17
Block: 1193185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49477 RingCT/type: yes/0
Extra: 0111ae885da268844717de01aa8e8d6aa9ba6fa21f27d3754cae10f0f92d08a0aa021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56717a52932fe1cbb6b1a97e76a1d9eef1a322814e182c559df896894fa089f1 0.600000000000 1679744 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": 1193195, "vin": [ { "gen": { "height": 1193185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56717a52932fe1cbb6b1a97e76a1d9eef1a322814e182c559df896894fa089f1" } } ], "extra": [ 1, 17, 174, 136, 93, 162, 104, 132, 71, 23, 222, 1, 170, 142, 141, 106, 169, 186, 111, 162, 31, 39, 211, 117, 76, 174, 16, 240, 249, 45, 8, 160, 170, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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