Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a65e6ec7055f9c51d8d460e7653fa954748124da761f2553c5dd20bef07960b2

Tx prefix hash: bcd2993f450f5e9a47e347174b86efd7b28cb5a11c66339c13f2e9b9e6d032ea
Tx public key: 0b4185e39fe482007aa7e86d8ec51745b680583208e889d24d6091e65406d3c7
Timestamp: 1629616698 Timestamp [UCT]: 2021-08-22 07:18:18 Age [y:d:h:m:s]: 03:298:20:20:03
Block: 318684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 987297 RingCT/type: yes/0
Extra: 010b4185e39fe482007aa7e86d8ec51745b680583208e889d24d6091e65406d3c702110000002db75ebe6a000000000000000000

1 output(s) for total of 53.960460170000 dcy

stealth address amount amount idx
00: 7d8ee4ae792c43547b3cd3aa3cc282cae94c5ed8e781e15cac221180d967fe20 53.960460170000 662321 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": 318694, "vin": [ { "gen": { "height": 318684 } } ], "vout": [ { "amount": 53960460170, "target": { "key": "7d8ee4ae792c43547b3cd3aa3cc282cae94c5ed8e781e15cac221180d967fe20" } } ], "extra": [ 1, 11, 65, 133, 227, 159, 228, 130, 0, 122, 167, 232, 109, 142, 197, 23, 69, 182, 128, 88, 50, 8, 232, 137, 210, 77, 96, 145, 230, 84, 6, 211, 199, 2, 17, 0, 0, 0, 45, 183, 94, 190, 106, 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