Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eee0146d9cd2e350cff8ba02d1bb2f254eff2fae8d2961d36a179d1ca6e9911

Tx prefix hash: 3be667b4317932335845a5c653a363879bdb1c509c338c76fb272527e8241930
Tx public key: 90c7e94a47b377a1417d2e2c9e83ab84520a7ceb276c2d574a4ffb1ad48c6fac
Timestamp: 1699567776 Timestamp [UCT]: 2023-11-09 22:09:36 Age [y:d:h:m:s]: 01:130:12:55:06
Block: 888168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354494 RingCT/type: yes/0
Extra: 0190c7e94a47b377a1417d2e2c9e83ab84520a7ceb276c2d574a4ffb1ad48c6fac02110000000233af99f4000000000000000000

1 output(s) for total of 0.700052677000 dcy

stealth address amount amount idx
00: f1d85dfafd63912f81d51800ab7355cf764bac90a60e280abf66179fb88b7a11 0.700052677000 1344097 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": 888178, "vin": [ { "gen": { "height": 888168 } } ], "vout": [ { "amount": 700052677, "target": { "key": "f1d85dfafd63912f81d51800ab7355cf764bac90a60e280abf66179fb88b7a11" } } ], "extra": [ 1, 144, 199, 233, 74, 71, 179, 119, 161, 65, 125, 46, 44, 158, 131, 171, 132, 82, 10, 124, 235, 39, 108, 45, 87, 74, 79, 251, 26, 212, 140, 111, 172, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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