For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 5629169f037f838b3c217250061ffdebb8b96767aee2c11cb1d4e1bd5bf00613
Tx prefix hash: b3ad6aa5daaff205b2a3b0b470904a7ae85da82e1c86ff51a90a8cbb384f5b65
Tx public key: 14605aa9520e99a3fd9df870f9e7ea45949628c3619d11eb615a5a8b4157e8ea
| Timestamp: 1781001746 | Timestamp [UTC]: 2026-06-09 10:42:26 | Age [y:d:h:m:s]: 00:006:00:31:34 |
| Block: 8464 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 281 | RingCT/type: yes/0 |
| Extra: 0114605aa9520e99a3fd9df870f9e7ea45949628c3619d11eb615a5a8b4157e8ea020900000001e49593ff00 | ||
1 output(s) for total of 34.620988506873 HMNY
| stealth address | amount | amount idx | tag |
| 00: 63ecc199ad5a50a5ef060800e3ac0d0cd81d7c534840e03c917bbffbb2253bb0 | 34.620988506873 | 10458 of 0 | <5d> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 8524,
"vin": [ {
"gen": {
"height": 8464
}
}
],
"vout": [ {
"amount": 34620988506873,
"target": {
"tagged_key": {
"key": "63ecc199ad5a50a5ef060800e3ac0d0cd81d7c534840e03c917bbffbb2253bb0",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 20, 96, 90, 169, 82, 14, 153, 163, 253, 157, 248, 112, 249, 231, 234, 69, 148, 150, 40, 195, 97, 157, 17, 235, 97, 90, 90, 139, 65, 87, 232, 234, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}