Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a62389bd4250cc1e5fdf11e77c2e173a29555466170949e96eca19ad18d38b87

Tx prefix hash: 0ddc2b3f5c02a2f55494b1ede771e96740d7cb0f241122dcc475c53b55200098
Tx public key: 0a458b2059bcdac7e6aeb3eb5f98fd1b84c2078d9b4a10bdec9ff287038620ab
Timestamp: 1729387270 Timestamp [UCT]: 2024-10-20 01:21:10 Age [y:d:h:m:s]: 00:148:09:59:22
Block: 1135375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105867 RingCT/type: yes/0
Extra: 010a458b2059bcdac7e6aeb3eb5f98fd1b84c2078d9b4a10bdec9ff287038620ab021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 431de464cd83dc8e5fd86405e55e2f238505e614fc57c98b1767d3548b2c8a5d 0.600000000000 1618712 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": 1135385, "vin": [ { "gen": { "height": 1135375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "431de464cd83dc8e5fd86405e55e2f238505e614fc57c98b1767d3548b2c8a5d" } } ], "extra": [ 1, 10, 69, 139, 32, 89, 188, 218, 199, 230, 174, 179, 235, 95, 152, 253, 27, 132, 194, 7, 141, 155, 74, 16, 189, 236, 159, 242, 135, 3, 134, 32, 171, 2, 17, 0, 0, 0, 2, 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