Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4cdba39dc349e7613d450860f3a98da0043a9f0ef3e5e785a176ef8d076d603

Tx prefix hash: c86958cffaedce9461c1aadd04dd42732cba36c0df10a67e02d610648314b416
Tx public key: 1ef8ab98aec9f20a2da33756f8bd2f19f09251d061cd58ed8e21f2402d40b355
Timestamp: 1658538427 Timestamp [UCT]: 2022-07-23 01:07:07 Age [y:d:h:m:s]: 02:297:08:18:53
Block: 549628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733734 RingCT/type: yes/0
Extra: 011ef8ab98aec9f20a2da33756f8bd2f19f09251d061cd58ed8e21f2402d40b35502110000000fa8c141c5000000000000000000

1 output(s) for total of 9.265191656000 dcy

stealth address amount amount idx
00: 67f1ef669113060b881fdf2f6eecf1698d7594acd68b7ef5a1e9be62e3491caf 9.265191656000 981017 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": 549638, "vin": [ { "gen": { "height": 549628 } } ], "vout": [ { "amount": 9265191656, "target": { "key": "67f1ef669113060b881fdf2f6eecf1698d7594acd68b7ef5a1e9be62e3491caf" } } ], "extra": [ 1, 30, 248, 171, 152, 174, 201, 242, 10, 45, 163, 55, 86, 248, 189, 47, 25, 240, 146, 81, 208, 97, 205, 88, 237, 142, 33, 242, 64, 45, 64, 179, 85, 2, 17, 0, 0, 0, 15, 168, 193, 65, 197, 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