Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f59c53e9dfbdcd4c9daab8db3c9a41db0b9e96f5b5ab61c763c41ca11ebebd

Tx prefix hash: 2a56a492402d9cdbcfd10c09ea3952280a9408a7498a11648443ee33dd0f5dd0
Tx public key: 07adecd1dc9277b9bdcba54df05a553cc9dd6efbb3d434796248cb53ac06d3d9
Timestamp: 1723239626 Timestamp [UCT]: 2024-08-09 21:40:26 Age [y:d:h:m:s]: 01:060:17:35:09
Block: 1084409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301834 RingCT/type: yes/0
Extra: 0107adecd1dc9277b9bdcba54df05a553cc9dd6efbb3d434796248cb53ac06d3d9021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b099f5ea84f72f920aff3bcdb4e6000080b2894903221dcba46539148d8df84f 0.600000000000 1558678 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": 1084419, "vin": [ { "gen": { "height": 1084409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b099f5ea84f72f920aff3bcdb4e6000080b2894903221dcba46539148d8df84f" } } ], "extra": [ 1, 7, 173, 236, 209, 220, 146, 119, 185, 189, 203, 165, 77, 240, 90, 85, 60, 201, 221, 110, 251, 179, 212, 52, 121, 98, 72, 203, 83, 172, 6, 211, 217, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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