Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b7c76d0e9e4d12b09f508e6ce2bf93d0a7e30434c9dd32a183a6f489c9b0c9

Tx prefix hash: 39cc2a2b6ce2fa4577cec3413e253f479298d4a0aa02d3a00bf0668bb0e5f581
Tx public key: c9f4177e7ccdf3676256948ce3327717858cf2a93ceb7eaf0079bc067617df6f
Timestamp: 1712851412 Timestamp [UCT]: 2024-04-11 16:03:32 Age [y:d:h:m:s]: 00:364:04:01:48
Block: 998265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260377 RingCT/type: yes/0
Extra: 01c9f4177e7ccdf3676256948ce3327717858cf2a93ceb7eaf0079bc067617df6f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb0ae1c36148ab6ec7290cf4685299a41ad197c26ee02961c7adbead230c8ef4 0.600000000000 1458711 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": 998275, "vin": [ { "gen": { "height": 998265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb0ae1c36148ab6ec7290cf4685299a41ad197c26ee02961c7adbead230c8ef4" } } ], "extra": [ 1, 201, 244, 23, 126, 124, 205, 243, 103, 98, 86, 148, 140, 227, 50, 119, 23, 133, 140, 242, 169, 60, 235, 126, 175, 0, 121, 188, 6, 118, 23, 223, 111, 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