Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e5ba6d25d43c3574907afca44d05c3ef2a2695889b075c51b67401a27b7a568

Tx prefix hash: 3b8ba4dd27c2465bbfb929e43b5d073da8a7614806b3d538391259bf45006a38
Tx public key: 779c693ffc2fe8301d68bc876bcace87a6fb48cf523bcf4aaf9cf768d036fdb1
Timestamp: 1632212300 Timestamp [UCT]: 2021-09-21 08:18:20 Age [y:d:h:m:s]: 03:169:15:52:32
Block: 338092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 897074 RingCT/type: yes/0
Extra: 01779c693ffc2fe8301d68bc876bcace87a6fb48cf523bcf4aaf9cf768d036fdb10211000000178d0de867000000000000000000

1 output(s) for total of 46.533025470000 dcy

stealth address amount amount idx
00: ed00dd3b38439341803c53cf1e0131ed7e5e65a4986d26372dc937bc5f6e5ad6 46.533025470000 695927 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": 338102, "vin": [ { "gen": { "height": 338092 } } ], "vout": [ { "amount": 46533025470, "target": { "key": "ed00dd3b38439341803c53cf1e0131ed7e5e65a4986d26372dc937bc5f6e5ad6" } } ], "extra": [ 1, 119, 156, 105, 63, 252, 47, 232, 48, 29, 104, 188, 135, 107, 202, 206, 135, 166, 251, 72, 207, 82, 59, 207, 74, 175, 156, 247, 104, 208, 54, 253, 177, 2, 17, 0, 0, 0, 23, 141, 13, 232, 103, 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