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: 533566fd0fc5df91add48e6f6e528eb678033114157153486a4a18d6928b8699
Tx prefix hash: a820f5d058d691b7d8f47f35ca7e59cd4e2d4cb5c2ad930c3a85dbfc710a8b0f
Tx public key: b4f5e14e1599e9cd0a835668ec51d877f6f66080f4c1a8b78b133b8da4fb4051
| Timestamp: 1779434379 | Timestamp [UTC]: 2026-05-22 07:19:39 | Age [y:d:h:m:s]: 00:017:18:16:18 |
| Block: 87 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7799 | RingCT/type: yes/0 |
| Extra: 01b4f5e14e1599e9cd0a835668ec51d877f6f66080f4c1a8b78b133b8da4fb4051020900000001a662ed0300 | ||
1 output(s) for total of 35.178601194456 HMNY
| stealth address | amount | amount idx | tag |
| 00: e2a0529c68b6471cb6acb286c663931dec4cf1789c46598b1468c94e0fad38fb | 35.178601194456 | 83 of 0 | <a6> |
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": 147,
"vin": [ {
"gen": {
"height": 87
}
}
],
"vout": [ {
"amount": 35178601194456,
"target": {
"tagged_key": {
"key": "e2a0529c68b6471cb6acb286c663931dec4cf1789c46598b1468c94e0fad38fb",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 180, 245, 225, 78, 21, 153, 233, 205, 10, 131, 86, 104, 236, 81, 216, 119, 246, 246, 96, 128, 244, 193, 168, 183, 139, 19, 59, 141, 164, 251, 64, 81, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}