Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f5359518afa843ee541521c153ea2a14ae43a4c2de7b4218898d7f22e536d6e

Tx prefix hash: 185da22813231beeffe0b8b4566e81a40179f61d17f3e5d5f0df0802d8ee1eca
Tx public key: 0826d1db7057258d3e650b8410f03f2c980ba92aafcdf76984e74b80b51d98a3
Timestamp: 1712991389 Timestamp [UCT]: 2024-04-13 06:56:29 Age [y:d:h:m:s]: 00:315:19:09:20
Block: 999430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225759 RingCT/type: yes/0
Extra: 010826d1db7057258d3e650b8410f03f2c980ba92aafcdf76984e74b80b51d98a30211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f71e040bfa08162e9d82646248c4854e3a225771194dc0acd0413a4137d2b47 0.600000000000 1459910 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": 999440, "vin": [ { "gen": { "height": 999430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f71e040bfa08162e9d82646248c4854e3a225771194dc0acd0413a4137d2b47" } } ], "extra": [ 1, 8, 38, 209, 219, 112, 87, 37, 141, 62, 101, 11, 132, 16, 240, 63, 44, 152, 11, 169, 42, 175, 205, 247, 105, 132, 231, 75, 128, 181, 29, 152, 163, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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