Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3db036ea20bd5f9c82fc1b0bfcc58c264dc6103c23d89db13f8fcdf9e7a5b58

Tx prefix hash: 659fa57428ed1ab9c8a0d0708757d899c3c041da484b6938c61aa5526cb50c24
Tx public key: 909c41ad7ef19187d355fa61e17b76d18a6368b32bf4c99e26d1a76d54075cf2
Timestamp: 1709421387 Timestamp [UCT]: 2024-03-02 23:16:27 Age [y:d:h:m:s]: 01:055:04:58:35
Block: 969856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300480 RingCT/type: yes/0
Extra: 01909c41ad7ef19187d355fa61e17b76d18a6368b32bf4c99e26d1a76d54075cf202110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68ed44bad5df61f41df36dd3cd587347c9a62450f7dd47e62c9ff871b28d1de3 0.600000000000 1429705 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": 969866, "vin": [ { "gen": { "height": 969856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68ed44bad5df61f41df36dd3cd587347c9a62450f7dd47e62c9ff871b28d1de3" } } ], "extra": [ 1, 144, 156, 65, 173, 126, 241, 145, 135, 211, 85, 250, 97, 225, 123, 118, 209, 138, 99, 104, 179, 43, 244, 201, 158, 38, 209, 167, 109, 84, 7, 92, 242, 2, 17, 0, 0, 0, 13, 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