Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00011ec67607c63d949da6e71d19a7dfafe191d9974d79ca5292bff4a0d258dc

Tx prefix hash: 1f40cfcf666e66d0a08107572482d533bdb1579419a023dbfe846981a0e4772e
Tx public key: ccca20d2699ae8ad80ee5f240cd113473688a322c701c0c2bc2bc94342092e6c
Timestamp: 1589363192 Timestamp [UCT]: 2020-05-13 09:46:32 Age [y:d:h:m:s]: 04:295:19:41:29
Block: 100426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131310 RingCT/type: yes/0
Extra: 01ccca20d2699ae8ad80ee5f240cd113473688a322c701c0c2bc2bc94342092e6c02110000029d39be35fb000000000000000000

1 output(s) for total of 285.264503691000 dcy

stealth address amount amount idx
00: 7e78c16e0520d59432422c81fafcabc77037eb8d4cb01379d98f0e73c5ef2527 285.264503691000 176946 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": 100436, "vin": [ { "gen": { "height": 100426 } } ], "vout": [ { "amount": 285264503691, "target": { "key": "7e78c16e0520d59432422c81fafcabc77037eb8d4cb01379d98f0e73c5ef2527" } } ], "extra": [ 1, 204, 202, 32, 210, 105, 154, 232, 173, 128, 238, 95, 36, 12, 209, 19, 71, 54, 136, 163, 34, 199, 1, 192, 194, 188, 43, 201, 67, 66, 9, 46, 108, 2, 17, 0, 0, 2, 157, 57, 190, 53, 251, 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