Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4242b3939dc8d09406fc0e1c7f3dab3f9853a1a4dbf9ad25042f8c4a5b291219

Tx prefix hash: 194db230006873fe32b6534cb615cb41e6773c1a0d1300a3a482e493d58b7f19
Tx public key: 2270e35594bc5dbd1928ffe616a20d4a9da5a351fa65e6209c34193eb6b771c4
Timestamp: 1705869748 Timestamp [UCT]: 2024-01-21 20:42:28 Age [y:d:h:m:s]: 01:291:13:21:45
Block: 940376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467204 RingCT/type: yes/0
Extra: 012270e35594bc5dbd1928ffe616a20d4a9da5a351fa65e6209c34193eb6b771c402110000001e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fcf2758cc6ae443c7f5c2e83e9613b2267eefc5cbc41705582136c2176723d2 0.600000000000 1398512 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": 940386, "vin": [ { "gen": { "height": 940376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fcf2758cc6ae443c7f5c2e83e9613b2267eefc5cbc41705582136c2176723d2" } } ], "extra": [ 1, 34, 112, 227, 85, 148, 188, 93, 189, 25, 40, 255, 230, 22, 162, 13, 74, 157, 165, 163, 81, 250, 101, 230, 32, 156, 52, 25, 62, 182, 183, 113, 196, 2, 17, 0, 0, 0, 30, 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