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: 94f91693929eb46de2352eca22cbf77e628fda068d325853593b4d49071f5cd1
Tx prefix hash: cd65857581dc63f3d8926dbedbc8bf604699db94eececc835ba24fc2c66836ca
Tx public key: 7788bef7db7d0f739adea725ee6a2c71d4e4a8d16a009e19efa7d1214e739566
| Timestamp: 1780998945 | Timestamp [UTC]: 2026-06-09 09:55:45 | Age [y:d:h:m:s]: 00:007:23:08:12 |
| Block: 8403 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 342 | RingCT/type: yes/0 |
| Extra: 017788bef7db7d0f739adea725ee6a2c71d4e4a8d16a009e19efa7d1214e739566020900000001e49593ff00 | ||
1 output(s) for total of 34.625016837056 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70bb63a8a20fb2f1fc4b6594e6a33654f1314f3ad759d48fa2998010f163467b | 34.625016837056 | 10387 of 0 | <9a> |
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": 8463,
"vin": [ {
"gen": {
"height": 8403
}
}
],
"vout": [ {
"amount": 34625016837056,
"target": {
"tagged_key": {
"key": "70bb63a8a20fb2f1fc4b6594e6a33654f1314f3ad759d48fa2998010f163467b",
"view_tag": "9a"
}
}
}
],
"extra": [ 1, 119, 136, 190, 247, 219, 125, 15, 115, 154, 222, 167, 37, 238, 106, 44, 113, 212, 228, 168, 209, 106, 0, 158, 25, 239, 167, 209, 33, 78, 115, 149, 102, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}