Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e96ae4fca4ab01113c5db46ba8cdbc61b24a643568960fc51b488006ecc45515

Tx prefix hash: 44300b76566b3a012c7b14c6af058aff88db527ea411a2fb3255cb146cb962db
Tx public key: 263f713d756f7287b42f8d3f02613dce413c585faad76c715770b95f9393f488
Timestamp: 1694890902 Timestamp [UCT]: 2023-09-16 19:01:42 Age [y:d:h:m:s]: 01:129:20:30:19
Block: 849577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354084 RingCT/type: yes/0
Extra: 01263f713d756f7287b42f8d3f02613dce413c585faad76c715770b95f9393f488021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.939760671000 dcy

stealth address amount amount idx
00: a9cce72d04cf66791e10c9d667a8194ef5f1c8122aff170d5ec97be169d47f36 0.939760671000 1303247 of 0

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": 849587, "vin": [ { "gen": { "height": 849577 } } ], "vout": [ { "amount": 939760671, "target": { "key": "a9cce72d04cf66791e10c9d667a8194ef5f1c8122aff170d5ec97be169d47f36" } } ], "extra": [ 1, 38, 63, 113, 61, 117, 111, 114, 135, 180, 47, 141, 63, 2, 97, 61, 206, 65, 60, 88, 95, 170, 215, 108, 113, 87, 112, 185, 95, 147, 147, 244, 136, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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