Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 099e7a44c630f7e523403011c1507916cd4bb37af05e545942c77b5f5dc402a6

Tx prefix hash: 06995236bb1f926f269755c7f91c2805afc434030e24e9407ba551d1b1577b6d
Tx public key: 83d3b4945179827a38b4b939e1b8ad02c8f02a9130c4847a05bc8fe902ca3285
Timestamp: 1636557332 Timestamp [UCT]: 2021-11-10 15:15:32 Age [y:d:h:m:s]: 03:089:07:38:07
Block: 371477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 842197 RingCT/type: yes/0
Extra: 0183d3b4945179827a38b4b939e1b8ad02c8f02a9130c4847a05bc8fe902ca32850211000000014f792ffd000000000000000000

1 output(s) for total of 36.070359358000 dcy

stealth address amount amount idx
00: 9cd7f3606e3f6d2a18085b6eb1830804c73eac79c507a55cc300bb38f2c19d92 36.070359358000 752787 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": 371487, "vin": [ { "gen": { "height": 371477 } } ], "vout": [ { "amount": 36070359358, "target": { "key": "9cd7f3606e3f6d2a18085b6eb1830804c73eac79c507a55cc300bb38f2c19d92" } } ], "extra": [ 1, 131, 211, 180, 148, 81, 121, 130, 122, 56, 180, 185, 57, 225, 184, 173, 2, 200, 240, 42, 145, 48, 196, 132, 122, 5, 188, 143, 233, 2, 202, 50, 133, 2, 17, 0, 0, 0, 1, 79, 121, 47, 253, 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