Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23909ce5ba77d44ddcb8b9d9a8eccc974a192e91f812c2475a1eec5fa889a1c5

Tx prefix hash: 2a871672e937f784c8eab4331c17333890e78574817be6f89f791324ad933f40
Tx public key: 6200e57703bc98e05b9cdc70f65d0602595c0f6890032ba274ac9454d3d853ad
Timestamp: 1634861616 Timestamp [UCT]: 2021-10-22 00:13:36 Age [y:d:h:m:s]: 03:188:00:44:02
Block: 357738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 912498 RingCT/type: yes/0
Extra: 016200e57703bc98e05b9cdc70f65d0602595c0f6890032ba274ac9454d3d853ad021100000001a272b9cb000000000000000000

1 output(s) for total of 40.055846503000 dcy

stealth address amount amount idx
00: 8b248f8fe2c345461afff381c647e03f2308f268e5a03925d6ca84104540a0c6 40.055846503000 729330 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": 357748, "vin": [ { "gen": { "height": 357738 } } ], "vout": [ { "amount": 40055846503, "target": { "key": "8b248f8fe2c345461afff381c647e03f2308f268e5a03925d6ca84104540a0c6" } } ], "extra": [ 1, 98, 0, 229, 119, 3, 188, 152, 224, 91, 156, 220, 112, 246, 93, 6, 2, 89, 92, 15, 104, 144, 3, 43, 162, 116, 172, 148, 84, 211, 216, 83, 173, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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