Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caca8679e03fb54e2288d41ff9ea9c0e4dcb8a026b80ecbb6da0d40ec33b9c6a

Tx prefix hash: 0fd3265c2d9c78a0d2a2e84ec9da463bfdd8c00e963836463110e7a4f4e6edf1
Tx public key: 0232687c80b0354e256bb45f386e0e3beb6ddc11931e4da5e3512509ec6ec439
Timestamp: 1705826077 Timestamp [UCT]: 2024-01-21 08:34:37 Age [y:d:h:m:s]: 01:037:15:45:35
Block: 940009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287987 RingCT/type: yes/0
Extra: 010232687c80b0354e256bb45f386e0e3beb6ddc11931e4da5e3512509ec6ec43902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa5c7213987fa8961a6afc5200b52b4952305de8fcc567b6539b13c839882e1c 0.600000000000 1398143 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": 940019, "vin": [ { "gen": { "height": 940009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa5c7213987fa8961a6afc5200b52b4952305de8fcc567b6539b13c839882e1c" } } ], "extra": [ 1, 2, 50, 104, 124, 128, 176, 53, 78, 37, 107, 180, 95, 56, 110, 14, 59, 235, 109, 220, 17, 147, 30, 77, 165, 227, 81, 37, 9, 236, 110, 196, 57, 2, 17, 0, 0, 0, 2, 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