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: 0867d7907e913294a14564ee08fc9f3bfc40d04168786c14ddfc44a4949e80b8
Tx prefix hash: 0406e2f3147eac4c1df26f4cbea964dc160def9aed42547a1c7b333e65ee24e8
Tx public key: bae0fc558e88709af318ba002e89f50e7404734eb3c5a8a7b4787dd0a99d18a7
| Timestamp: 1780808059 | Timestamp [UTC]: 2026-06-07 04:54:19 | Age [y:d:h:m:s]: 00:001:20:41:38 |
| Block: 6980 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 906 | RingCT/type: yes/0 |
| Extra: 01bae0fc558e88709af318ba002e89f50e7404734eb3c5a8a7b4787dd0a99d18a7020900000002e49593ff00 | ||
1 output(s) for total of 34.719122312996 HMNY
| stealth address | amount | amount idx | tag |
| 00: 88e59949d0337923d3d90ad48389bca92bd3ea39a14254d78730317fafe2784c | 34.719122312996 | 8608 of 0 | <63> |
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": 7040,
"vin": [ {
"gen": {
"height": 6980
}
}
],
"vout": [ {
"amount": 34719122312996,
"target": {
"tagged_key": {
"key": "88e59949d0337923d3d90ad48389bca92bd3ea39a14254d78730317fafe2784c",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 186, 224, 252, 85, 142, 136, 112, 154, 243, 24, 186, 0, 46, 137, 245, 14, 116, 4, 115, 78, 179, 197, 168, 167, 180, 120, 125, 208, 169, 157, 24, 167, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}