Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ee108e06168f047ec358b7f6ce07978fbfb755191da6e5e114fbc835852c7c

Tx prefix hash: 4470afd16e16dda7a7b23b952d40d000c8ee7f3680210e8b0d0f9cf4b5955503
Tx public key: aaccfd850fa02af7bda5e1d371e52db79d6444b914d92831c59f1311ce881197
Timestamp: 1696994756 Timestamp [UCT]: 2023-10-11 03:25:56 Age [y:d:h:m:s]: 01:178:20:14:30
Block: 867035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388837 RingCT/type: yes/0
Extra: 01aaccfd850fa02af7bda5e1d371e52db79d6444b914d92831c59f1311ce8811970211000000094b8f5122000000000000000000

1 output(s) for total of 0.822532664000 dcy

stealth address amount amount idx
00: 0f74e00dd968cf358a16da9ddef98daaf2cc2a3a1497eaf74f1788615e26c751 0.822532664000 1321683 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": 867045, "vin": [ { "gen": { "height": 867035 } } ], "vout": [ { "amount": 822532664, "target": { "key": "0f74e00dd968cf358a16da9ddef98daaf2cc2a3a1497eaf74f1788615e26c751" } } ], "extra": [ 1, 170, 204, 253, 133, 15, 160, 42, 247, 189, 165, 225, 211, 113, 229, 45, 183, 157, 100, 68, 185, 20, 217, 40, 49, 197, 159, 19, 17, 206, 136, 17, 151, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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