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: b17f51872327cb5ccdb1ef5a67f314968fbd8e79e3a28a65888c4b1c0a71209b
Tx prefix hash: 8a1b2c232882e80aa4e7c2b75fceaf0115da1696ed1c3f061c0366e7d829fb3f
Tx public key: 7bd71ef6e736e7d83d8fe1adf8bb206dc4c04c6621c58a4dccdc9ec813758df7
| Timestamp: 1779633310 | Timestamp [UTC]: 2026-05-24 14:35:10 | Age [y:d:h:m:s]: 00:015:12:14:38 |
| Block: 979 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6941 | RingCT/type: yes/0 |
| Extra: 017bd71ef6e736e7d83d8fe1adf8bb206dc4c04c6621c58a4dccdc9ec813758df7020900000001ba6d17be00 | ||
1 output(s) for total of 35.118800734408 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad0c6c13c77f354a549dfb3ab5a23e6f130e80aa77c128607726a0dc51e742b3 | 35.118800734408 | 1115 of 0 | <b2> |
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": 1039,
"vin": [ {
"gen": {
"height": 979
}
}
],
"vout": [ {
"amount": 35118800734408,
"target": {
"tagged_key": {
"key": "ad0c6c13c77f354a549dfb3ab5a23e6f130e80aa77c128607726a0dc51e742b3",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 123, 215, 30, 246, 231, 54, 231, 216, 61, 143, 225, 173, 248, 187, 32, 109, 196, 192, 76, 102, 33, 197, 138, 77, 204, 220, 158, 200, 19, 117, 141, 247, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}