Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5a155647b6b49b55b53a8430c57b06d9f8c6153fc2c62828cce0de5d00ceb35

Tx prefix hash: 0fb6ff9ed0d89fb85a50258b566839ab5e95a65436dd2e6f653cb91498dd98cd
Tx public key: 760321a2758236aad6d38a7cf0728cb4ec8aa610d6519037944787a1fa6c03e3
Timestamp: 1581571029 Timestamp [UCT]: 2020-02-13 05:17:09 Age [y:d:h:m:s]: 04:329:06:00:12
Block: 63942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127484 RingCT/type: yes/0
Extra: 01760321a2758236aad6d38a7cf0728cb4ec8aa610d6519037944787a1fa6c03e302110000000156c366d3000000000000000000

1 output(s) for total of 376.820414512000 dcy

stealth address amount amount idx
00: 5bc7e8430374807b5e0fbd2710e072ce2627e5704b182feaf3900d925ccec7bf 376.820414512000 117851 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": 63952, "vin": [ { "gen": { "height": 63942 } } ], "vout": [ { "amount": 376820414512, "target": { "key": "5bc7e8430374807b5e0fbd2710e072ce2627e5704b182feaf3900d925ccec7bf" } } ], "extra": [ 1, 118, 3, 33, 162, 117, 130, 54, 170, 214, 211, 138, 124, 240, 114, 140, 180, 236, 138, 166, 16, 214, 81, 144, 55, 148, 71, 135, 161, 250, 108, 3, 227, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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