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: a70f8376e1e03e7a44825bd330f527fd53f8aaa4eca1b1d5bc5fef1317765a16
Tx prefix hash: 04fe8bef5a88c67d2a5d3de6a981c9d824ad4f19fa72e74496ba0f0b0fb79c83
Tx public key: 23d821dea613fe27514c0b0eb65704c7dfe9ddab74ef6815e25466998fa2ce29
| Timestamp: 1781004633 | Timestamp [UTC]: 2026-06-09 11:30:33 | Age [y:d:h:m:s]: 00:007:21:44:33 |
| Block: 8514 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 231 | RingCT/type: yes/0 |
| Extra: 0123d821dea613fe27514c0b0eb65704c7dfe9ddab74ef6815e25466998fa2ce29020900000001e49593ff00 | ||
1 output(s) for total of 34.617686946403 HMNY
| stealth address | amount | amount idx | tag |
| 00: b995f28766f9405699d7cedf106836b118f43b253d48cc6e53f39946d3d2663b | 34.617686946403 | 10518 of 0 | <a7> |
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": 8574,
"vin": [ {
"gen": {
"height": 8514
}
}
],
"vout": [ {
"amount": 34617686946403,
"target": {
"tagged_key": {
"key": "b995f28766f9405699d7cedf106836b118f43b253d48cc6e53f39946d3d2663b",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 35, 216, 33, 222, 166, 19, 254, 39, 81, 76, 11, 14, 182, 87, 4, 199, 223, 233, 221, 171, 116, 239, 104, 21, 226, 84, 102, 153, 143, 162, 206, 41, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}