Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afea6782e47b7ff0d3aeda9e912eeece480b132b6346dedb3dd4e590bb4754f1

Tx prefix hash: 1da8e043ff88fb7532b52bc0bf49b06d2a2a378a8d7fad9018c62abfa4ab426b
Tx public key: 22cc281a9d11d68baa76bf334f7b95e04a4c7765706fbd0a95d57384c770c094
Timestamp: 1701161039 Timestamp [UCT]: 2023-11-28 08:43:59 Age [y:d:h:m:s]: 02:029:18:45:55
Block: 901367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541107 RingCT/type: yes/0
Extra: 0122cc281a9d11d68baa76bf334f7b95e04a4c7765706fbd0a95d57384c770c0940211000000064b8f5122000000000000000000

1 output(s) for total of 0.632990125000 dcy

stealth address amount amount idx
00: ef9bde1ce866c263c2b213aa5cccc02413c7802ce5f940ce6212238135d41140 0.632990125000 1357926 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": 901377, "vin": [ { "gen": { "height": 901367 } } ], "vout": [ { "amount": 632990125, "target": { "key": "ef9bde1ce866c263c2b213aa5cccc02413c7802ce5f940ce6212238135d41140" } } ], "extra": [ 1, 34, 204, 40, 26, 157, 17, 214, 139, 170, 118, 191, 51, 79, 123, 149, 224, 74, 76, 119, 101, 112, 111, 189, 10, 149, 213, 115, 132, 199, 112, 192, 148, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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