Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75b20258214c8164c5bfa6eca7bca64ca40690f9e53cc7afe1dd51c09ba2ea6

Tx prefix hash: d46cda8448034aa05efad58b2b43e74ec489cd7614ad6337066c6c8c7f1a1c83
Tx public key: 6f7d51d0f8e571749cb834341278b628b797c9a56000302b860926e48c5efb83
Timestamp: 1721841502 Timestamp [UCT]: 2024-07-24 17:18:22 Age [y:d:h:m:s]: 00:258:16:20:33
Block: 1072814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184801 RingCT/type: yes/0
Extra: 016f7d51d0f8e571749cb834341278b628b797c9a56000302b860926e48c5efb8302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaf26d089533e5de095f39e79d227b6bfa0c7b5039fa354fa1899afd239e7002 0.600000000000 1545311 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": 1072824, "vin": [ { "gen": { "height": 1072814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaf26d089533e5de095f39e79d227b6bfa0c7b5039fa354fa1899afd239e7002" } } ], "extra": [ 1, 111, 125, 81, 208, 248, 229, 113, 116, 156, 184, 52, 52, 18, 120, 182, 40, 183, 151, 201, 165, 96, 0, 48, 43, 134, 9, 38, 228, 140, 94, 251, 131, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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