Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3509c163347d0048ed6d1080c53fbdd57331a023851143f46dbbefad3ada74

Tx prefix hash: fa08ea6239d7c114253052f45e1579707b0e74da98be8b2a9669339e77e4ca47
Tx public key: 1f97960f1b9c535d7d0e84481c7e59c0aa28df2c6d249c237a5795ca65328734
Timestamp: 1708518495 Timestamp [UCT]: 2024-02-21 12:28:15 Age [y:d:h:m:s]: 01:085:16:52:30
Block: 962373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322294 RingCT/type: yes/0
Extra: 011f97960f1b9c535d7d0e84481c7e59c0aa28df2c6d249c237a5795ca6532873402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3bb8710d42727de086edd9fb7706413f4452e1346e37cd1db5c4ee9865e55c3 0.600000000000 1422006 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": 962383, "vin": [ { "gen": { "height": 962373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3bb8710d42727de086edd9fb7706413f4452e1346e37cd1db5c4ee9865e55c3" } } ], "extra": [ 1, 31, 151, 150, 15, 27, 156, 83, 93, 125, 14, 132, 72, 28, 126, 89, 192, 170, 40, 223, 44, 109, 36, 156, 35, 122, 87, 149, 202, 101, 50, 135, 52, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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