Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcaf849478adb9f9e3077dcdd99399e48f7377ec9f07712fa971dca8d38e1b83

Tx prefix hash: 332dad711c88ecc42572c6568ebc42d5dceb6166bf5e49b7ef15c538d88a68d7
Tx public key: 6a3156a5ec807289bd82413b37c0a68f18e365449d689f776106bef81baa1176
Timestamp: 1608834817 Timestamp [UCT]: 2020-12-24 18:33:37 Age [y:d:h:m:s]: 04:012:05:30:40
Block: 168636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1021738 RingCT/type: yes/0
Extra: 016a3156a5ec807289bd82413b37c0a68f18e365449d689f776106bef81baa11760211000001a8b9b01d0b000000000000000000

1 output(s) for total of 169.536070650000 dcy

stealth address amount amount idx
00: 63c0deb4cc1db0b758fee09e017bd6c5798652dcf4f9b4c85a55e0dc99730d13 169.536070650000 313307 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": 168646, "vin": [ { "gen": { "height": 168636 } } ], "vout": [ { "amount": 169536070650, "target": { "key": "63c0deb4cc1db0b758fee09e017bd6c5798652dcf4f9b4c85a55e0dc99730d13" } } ], "extra": [ 1, 106, 49, 86, 165, 236, 128, 114, 137, 189, 130, 65, 59, 55, 192, 166, 143, 24, 227, 101, 68, 157, 104, 159, 119, 97, 6, 190, 248, 27, 170, 17, 118, 2, 17, 0, 0, 1, 168, 185, 176, 29, 11, 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