Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 006c97ccd6d3298a8f7b1d046e67804897fbbbf89d7ed701657bc945d9a570ce

Tx prefix hash: ab8b3977997fd3e8c8c9a7ae450689e7f1c88e56f40012b3970e5674496dcd1b
Tx public key: 3c416f0ee4bf9f552caaecee3aa37b867610849301e04db0ff667152e94d08a3
Timestamp: 1702413104 Timestamp [UCT]: 2023-12-12 20:31:44 Age [y:d:h:m:s]: 01:038:20:17:24
Block: 911769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289068 RingCT/type: yes/0
Extra: 013c416f0ee4bf9f552caaecee3aa37b867610849301e04db0ff667152e94d08a302110000000833af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddc0063c956297e12dddb341c64694ca1608189b6f58ebf1c40b406aea114a50 0.600000000000 1368985 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": 911779, "vin": [ { "gen": { "height": 911769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddc0063c956297e12dddb341c64694ca1608189b6f58ebf1c40b406aea114a50" } } ], "extra": [ 1, 60, 65, 111, 14, 228, 191, 159, 85, 44, 170, 236, 238, 58, 163, 123, 134, 118, 16, 132, 147, 1, 224, 77, 176, 255, 102, 113, 82, 233, 77, 8, 163, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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