Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ebc84969562a3c8a31f952cd91a467c77d47b02af5ca2da649ee2a4613bd5f

Tx prefix hash: 2e7e9123980d52875c69622cdb35b87d658f42a4296b60eb35b6c062792f2c28
Tx public key: 052efa8abaf0a021664e036bc30447d66c82d703c29f252ec8cb402f3441cb60
Timestamp: 1709013762 Timestamp [UCT]: 2024-02-27 06:02:42 Age [y:d:h:m:s]: 01:058:10:39:54
Block: 966483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302795 RingCT/type: yes/0
Extra: 01052efa8abaf0a021664e036bc30447d66c82d703c29f252ec8cb402f3441cb600211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feb6a551354b165db90f3162e4bc3248acca7a3786df754a47bfaf74b4fde9e0 0.600000000000 1426240 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": 966493, "vin": [ { "gen": { "height": 966483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feb6a551354b165db90f3162e4bc3248acca7a3786df754a47bfaf74b4fde9e0" } } ], "extra": [ 1, 5, 46, 250, 138, 186, 240, 160, 33, 102, 78, 3, 107, 195, 4, 71, 214, 108, 130, 215, 3, 194, 159, 37, 46, 200, 203, 64, 47, 52, 65, 203, 96, 2, 17, 0, 0, 0, 1, 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