Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91d11d60627385815360fd31092bd424f8c638c54791847d7c342518a819b7fa

Tx prefix hash: da7f4730a256cb2c6930af940e55a0f64ca377da1b1e0d5060e1c364bd746d4f
Tx public key: 92e67bf380356a07f46421b92f0ebdcfab6458f19ec1795d8ab5c93c41a59e36
Timestamp: 1708617334 Timestamp [UCT]: 2024-02-22 15:55:34 Age [y:d:h:m:s]: 01:117:20:27:29
Block: 963182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345164 RingCT/type: yes/0
Extra: 0192e67bf380356a07f46421b92f0ebdcfab6458f19ec1795d8ab5c93c41a59e3602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8d44d969c6ae22e8f73dfcb9b7227931a192f2d17dd2de1c86e9d725411bef3 0.600000000000 1422881 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": 963192, "vin": [ { "gen": { "height": 963182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8d44d969c6ae22e8f73dfcb9b7227931a192f2d17dd2de1c86e9d725411bef3" } } ], "extra": [ 1, 146, 230, 123, 243, 128, 53, 106, 7, 244, 100, 33, 185, 47, 14, 189, 207, 171, 100, 88, 241, 158, 193, 121, 93, 138, 181, 201, 60, 65, 165, 158, 54, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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