Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ac2c93f92fcf6eaabb3f951b6d35160cfedc473875e183b1ecf815a41e57cc

Tx prefix hash: 7287e7806a98dc44366c2750270a1e13766d0c22daf459fcbbfa2e1aaafa0b8e
Tx public key: 602f0e5b1a606c43c4059ce74d32159354d3767a844562a3340a78919f9c91e8
Timestamp: 1733093168 Timestamp [UCT]: 2024-12-01 22:46:08 Age [y:d:h:m:s]: 00:124:18:05:35
Block: 1166005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88962 RingCT/type: yes/0
Extra: 01602f0e5b1a606c43c4059ce74d32159354d3767a844562a3340a78919f9c91e8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dacec945fdcd62474a1c3eff9dd0f14d278f8024e8f435fb82bcb84a45978ee 0.600000000000 1651682 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": 1166015, "vin": [ { "gen": { "height": 1166005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dacec945fdcd62474a1c3eff9dd0f14d278f8024e8f435fb82bcb84a45978ee" } } ], "extra": [ 1, 96, 47, 14, 91, 26, 96, 108, 67, 196, 5, 156, 231, 77, 50, 21, 147, 84, 211, 118, 122, 132, 69, 98, 163, 52, 10, 120, 145, 159, 156, 145, 232, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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