Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ab16f785972560d1c9ac3187cf1f676c63bd2d1589ea954975254cf753cf764

Tx prefix hash: 99daec1007f9b3801a3002586240cb2079cf43adcdc0d5628294bbfb24d0d7dc
Tx public key: ed9f1214cdd905addf7f9ca0babbb63a24ca306f31b7e80558ee05fb91ea9bd8
Timestamp: 1709038147 Timestamp [UCT]: 2024-02-27 12:49:07 Age [y:d:h:m:s]: 01:016:10:34:33
Block: 966685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272759 RingCT/type: yes/0
Extra: 01ed9f1214cdd905addf7f9ca0babbb63a24ca306f31b7e80558ee05fb91ea9bd80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f929d5519deec5c98bb46cfc9c943a55fd33d6ec919d3aa13ccfab3e906c05f5 0.600000000000 1426454 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": 966695, "vin": [ { "gen": { "height": 966685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f929d5519deec5c98bb46cfc9c943a55fd33d6ec919d3aa13ccfab3e906c05f5" } } ], "extra": [ 1, 237, 159, 18, 20, 205, 217, 5, 173, 223, 127, 156, 160, 186, 187, 182, 58, 36, 202, 48, 111, 49, 183, 232, 5, 88, 238, 5, 251, 145, 234, 155, 216, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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