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: 8a26a716a225851f82c1e7b4b65d1ba694565e5b35f857653dcbfb790b51f94a
Tx prefix hash: dd71e74503cd4199646140f6b7c211c2d5f30c5769e2beac30342d1073149f66
Tx public key: 3cacf4d5cf4dc63bb77914498e172d5fe949fe4ad09e36d9cec5c25e2310103e
| Timestamp: 1779520276 | Timestamp [UTC]: 2026-05-23 07:11:16 | Age [y:d:h:m:s]: 00:016:20:27:34 |
| Block: 680 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7269 | RingCT/type: yes/0 |
| Extra: 013cacf4d5cf4dc63bb77914498e172d5fe949fe4ad09e36d9cec5c25e2310103e02090000003eba6d17be00 | ||
1 output(s) for total of 35.141438620779 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75f6dedf17c1683338705fe04628975a77ed10602e2730fe66ce25c4adf975f4 | 35.141438620779 | 753 of 0 | <88> |
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": 740,
"vin": [ {
"gen": {
"height": 680
}
}
],
"vout": [ {
"amount": 35141438620779,
"target": {
"tagged_key": {
"key": "75f6dedf17c1683338705fe04628975a77ed10602e2730fe66ce25c4adf975f4",
"view_tag": "88"
}
}
}
],
"extra": [ 1, 60, 172, 244, 213, 207, 77, 198, 59, 183, 121, 20, 73, 142, 23, 45, 95, 233, 73, 254, 74, 208, 158, 54, 217, 206, 197, 194, 94, 35, 16, 16, 62, 2, 9, 0, 0, 0, 62, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}