Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f8249479da22c22637e7b21f0b0217c746cd80875c3ee9c3bf324bb8f61d25a

Tx prefix hash: e4e31f2513d5dbbb2737b09aa98a83f1056bdf6a92d32bb12cf02438275dd07c
Tx public key: 12badff21e2db9a5bfd30be574ee82f5cb6728159b236fa1902e3d6784a5b96a
Timestamp: 1708648171 Timestamp [UCT]: 2024-02-23 00:29:31 Age [y:d:h:m:s]: 01:041:23:24:38
Block: 963444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291019 RingCT/type: yes/0
Extra: 0112badff21e2db9a5bfd30be574ee82f5cb6728159b236fa1902e3d6784a5b96a0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31a4b84a11ca8a75c030085f8e2bee999323bfb60cc1ae676db167c529acbd1a 0.600000000000 1423155 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": 963454, "vin": [ { "gen": { "height": 963444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31a4b84a11ca8a75c030085f8e2bee999323bfb60cc1ae676db167c529acbd1a" } } ], "extra": [ 1, 18, 186, 223, 242, 30, 45, 185, 165, 191, 211, 11, 229, 116, 238, 130, 245, 203, 103, 40, 21, 155, 35, 111, 161, 144, 46, 61, 103, 132, 165, 185, 106, 2, 17, 0, 0, 0, 9, 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