Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e91b19866869bb74dc67ba394b49c42c43b3d2378d493f9c5d00139010052dd

Tx prefix hash: d76f07758b6ed70cd650b12c3f3c5ee8f7f0b4820d0e321d37d9ea8bece57b60
Tx public key: fee9a42a3fdcfbecf2a7c0e136f9ba2c36239212563e6313119e5a656657e766
Timestamp: 1581823407 Timestamp [UCT]: 2020-02-16 03:23:27 Age [y:d:h:m:s]: 04:276:20:39:13
Block: 65904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090121 RingCT/type: yes/0
Extra: 01fee9a42a3fdcfbecf2a7c0e136f9ba2c36239212563e6313119e5a656657e76602112dba5bc700000000000000000000000000

1 output(s) for total of 371.221823412000 dcy

stealth address amount amount idx
00: 46d5edcd33b4dc56be6d8e6da545c1b71ef2ce6a9e2e53755a824b32f173a8d8 371.221823412000 121525 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": 65914, "vin": [ { "gen": { "height": 65904 } } ], "vout": [ { "amount": 371221823412, "target": { "key": "46d5edcd33b4dc56be6d8e6da545c1b71ef2ce6a9e2e53755a824b32f173a8d8" } } ], "extra": [ 1, 254, 233, 164, 42, 63, 220, 251, 236, 242, 167, 192, 225, 54, 249, 186, 44, 54, 35, 146, 18, 86, 62, 99, 19, 17, 158, 90, 101, 102, 87, 231, 102, 2, 17, 45, 186, 91, 199, 0, 0, 0, 0, 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