Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10e65d5373187276fae851ccd023f8ec4c948d122d63f720f28f28cb2ed273be

Tx prefix hash: 7122e98661e5e7cce70cc11f05f7ea558cf25bf18811610479f3e1a73dfaa50f
Tx public key: a7b22f7dacb1c026cd39178dab9b0e1877aedf239e8eec66ff9fac4fd5d291e2
Timestamp: 1703427694 Timestamp [UCT]: 2023-12-24 14:21:34 Age [y:d:h:m:s]: 01:333:00:20:04
Block: 920166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496847 RingCT/type: yes/0
Extra: 01a7b22f7dacb1c026cd39178dab9b0e1877aedf239e8eec66ff9fac4fd5d291e2021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67b3f29716e260f6bbe8ae4f19a3c2c963be1226156720582659d340aa8954b7 0.600000000000 1377844 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": 920176, "vin": [ { "gen": { "height": 920166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67b3f29716e260f6bbe8ae4f19a3c2c963be1226156720582659d340aa8954b7" } } ], "extra": [ 1, 167, 178, 47, 125, 172, 177, 192, 38, 205, 57, 23, 141, 171, 155, 14, 24, 119, 174, 223, 35, 158, 142, 236, 102, 255, 159, 172, 79, 213, 210, 145, 226, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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