Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e396705c3967583dc02d14c4c389735b42f4d9980a6595077fe5a08b0265731c

Tx prefix hash: 0b9c1d629a66bb3d9cb412b6a5838221072c1951d676f5940051c6351d20c1d2
Tx public key: 10c23d3bc52b4a7f9b16133e24dc15cf153c165c0ce384a7e5eedfb3c49b64b4
Timestamp: 1704457152 Timestamp [UCT]: 2024-01-05 12:19:12 Age [y:d:h:m:s]: 00:362:01:53:19
Block: 928676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259252 RingCT/type: yes/0
Extra: 0110c23d3bc52b4a7f9b16133e24dc15cf153c165c0ce384a7e5eedfb3c49b64b40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 478d623caee352652e6e554d70a6e4e2febe3859c0bc153394109beb8ef85676 0.600000000000 1386536 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": 928686, "vin": [ { "gen": { "height": 928676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "478d623caee352652e6e554d70a6e4e2febe3859c0bc153394109beb8ef85676" } } ], "extra": [ 1, 16, 194, 61, 59, 197, 43, 74, 127, 155, 22, 19, 62, 36, 220, 21, 207, 21, 60, 22, 92, 12, 227, 132, 167, 229, 238, 223, 179, 196, 155, 100, 180, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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