Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe05bf335cd2a36bd0460b61b2bc9e126603b93089adb9a95d82f1de5c1abb97

Tx prefix hash: db6539b03adc35ae3e79399def454118a47bac76bff984a0151fc6d39262c463
Tx public key: 96c2a2a3f257e745595c70016b8e2b4ccb2889268dbf65f983dac8436df7691c
Timestamp: 1707852613 Timestamp [UCT]: 2024-02-13 19:30:13 Age [y:d:h:m:s]: 00:252:14:00:50
Block: 956846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180895 RingCT/type: yes/0
Extra: 0196c2a2a3f257e745595c70016b8e2b4ccb2889268dbf65f983dac8436df7691c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 381ab7112da16d19d1d193a94ce478e663b9a0ff4f01ee651572c9bb3d22c87a 0.600000000000 1416156 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": 956856, "vin": [ { "gen": { "height": 956846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "381ab7112da16d19d1d193a94ce478e663b9a0ff4f01ee651572c9bb3d22c87a" } } ], "extra": [ 1, 150, 194, 162, 163, 242, 87, 231, 69, 89, 92, 112, 1, 107, 142, 43, 76, 203, 40, 137, 38, 141, 191, 101, 249, 131, 218, 200, 67, 109, 247, 105, 28, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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