Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: def3c9b4da6361c3abaa2ab3fb8bab96ad1d9c335c86077ca007e853de8fdaa7

Tx prefix hash: a9ffb88779ffbc955b69e02a7b8ae209b693f12709872d1037e8104ffbd937c0
Tx public key: f66dcb0daa49c55302575d6f2819cee3c126d0c5c9dff56a83ab87a99475fe68
Timestamp: 1707011804 Timestamp [UCT]: 2024-02-04 01:56:44 Age [y:d:h:m:s]: 01:276:06:44:00
Block: 949858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456224 RingCT/type: yes/0
Extra: 01f66dcb0daa49c55302575d6f2819cee3c126d0c5c9dff56a83ab87a99475fe6802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87a8dcd7eb753d6c915b51fd3136642f872d613124834ab2a70f22251b78aeaa 0.600000000000 1408392 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": 949868, "vin": [ { "gen": { "height": 949858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87a8dcd7eb753d6c915b51fd3136642f872d613124834ab2a70f22251b78aeaa" } } ], "extra": [ 1, 246, 109, 203, 13, 170, 73, 197, 83, 2, 87, 93, 111, 40, 25, 206, 227, 193, 38, 208, 197, 201, 223, 245, 106, 131, 171, 135, 169, 148, 117, 254, 104, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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