Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86b8199a7a880101ac3469888160f91d8b8431f69e7295b91e51997aaf53f5f5

Tx prefix hash: 79331c63afae0f3d13e37f8bab250b1e8848cb2ccdc7dc56a6c076ffdb0ee4f0
Tx public key: 88cff7a65ed90adf06fc0fb3a8c47a42f433519a9689f9bc5b8cfbb174b09ee2
Timestamp: 1723763014 Timestamp [UCT]: 2024-08-15 23:03:34 Age [y:d:h:m:s]: 00:129:07:23:09
Block: 1088757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92531 RingCT/type: yes/0
Extra: 0188cff7a65ed90adf06fc0fb3a8c47a42f433519a9689f9bc5b8cfbb174b09ee2021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e9c19dedc1e6f604e0577929906cc6df8114b471c1774e92a215739f41eda83 0.600000000000 1563376 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": 1088767, "vin": [ { "gen": { "height": 1088757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e9c19dedc1e6f604e0577929906cc6df8114b471c1774e92a215739f41eda83" } } ], "extra": [ 1, 136, 207, 247, 166, 94, 217, 10, 223, 6, 252, 15, 179, 168, 196, 122, 66, 244, 51, 81, 154, 150, 137, 249, 188, 91, 140, 251, 177, 116, 176, 158, 226, 2, 17, 0, 0, 0, 1, 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