Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d4b829143a3413eac0158fd66116106897cc181c0ddc749d65a1e2a37454ee2

Tx prefix hash: 5b732dc5bc9e4ee6b8f86ab663417416e64a6b417863912b5e87846f1ece150c
Tx public key: f954e90465f13b8eadcc7ae0f7b1b0e44bb4bdb2d3acdbdf65cdae87d7e91982
Timestamp: 1666030375 Timestamp [UCT]: 2022-10-17 18:12:55 Age [y:d:h:m:s]: 02:130:18:27:46
Block: 611157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 615059 RingCT/type: yes/0
Extra: 01f954e90465f13b8eadcc7ae0f7b1b0e44bb4bdb2d3acdbdf65cdae87d7e9198202110000000675e3f0e9000000000000000000

1 output(s) for total of 5.794062814000 dcy

stealth address amount amount idx
00: 8be0c43474c7c5b97ab2d08f5b4e543925e6dc72207d908bd991c49bc2490504 5.794062814000 1048213 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": 611167, "vin": [ { "gen": { "height": 611157 } } ], "vout": [ { "amount": 5794062814, "target": { "key": "8be0c43474c7c5b97ab2d08f5b4e543925e6dc72207d908bd991c49bc2490504" } } ], "extra": [ 1, 249, 84, 233, 4, 101, 241, 59, 142, 173, 204, 122, 224, 247, 177, 176, 228, 75, 180, 189, 178, 211, 172, 219, 223, 101, 205, 174, 135, 215, 233, 25, 130, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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