Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1f0fc72233d115800672a4d11c8932a78777cc2c9bae4539261c9a31481deb4

Tx prefix hash: ae26056f4a5dc8b1f143bb1fcd10a1872d043f9b09e527859c9e8d3989984dd8
Tx public key: 6fac3fb555f8d39e2e7d6cf2efb77dccc12968277f6832b74c7731e0f9e8ee55
Timestamp: 1617462022 Timestamp [UCT]: 2021-04-03 15:00:22 Age [y:d:h:m:s]: 03:237:09:24:20
Block: 232503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 929252 RingCT/type: yes/0
Extra: 016fac3fb555f8d39e2e7d6cf2efb77dccc12968277f6832b74c7731e0f9e8ee5502110000003ef18a1c63000000000000000000

1 output(s) for total of 104.140970921000 dcy

stealth address amount amount idx
00: deecb3b654163be6b565e5e9e6f2ffb9f3f54f9af423d5c2ece4e72d3bc64b9a 104.140970921000 483063 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": 232513, "vin": [ { "gen": { "height": 232503 } } ], "vout": [ { "amount": 104140970921, "target": { "key": "deecb3b654163be6b565e5e9e6f2ffb9f3f54f9af423d5c2ece4e72d3bc64b9a" } } ], "extra": [ 1, 111, 172, 63, 181, 85, 248, 211, 158, 46, 125, 108, 242, 239, 183, 125, 204, 193, 41, 104, 39, 127, 104, 50, 183, 76, 119, 49, 224, 249, 232, 238, 85, 2, 17, 0, 0, 0, 62, 241, 138, 28, 99, 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