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: 7433d90257fa24908134353e3d39b36bbb993920333bb9081f14c0ebbe28759d
Tx prefix hash: 95bcb6ee4763fc092557d7c0607382e54664c0939bb203a697d3ebe24efc8e62
Tx public key: e4197d4dc29f5009be30c444bb04dd2afb91d2b34e9dbd734cb920c4af79e1b3
| Timestamp: 1780809480 | Timestamp [UTC]: 2026-06-07 05:18:00 | Age [y:d:h:m:s]: 00:001:20:17:57 |
| Block: 7000 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 886 | RingCT/type: yes/0 |
| Extra: 01e4197d4dc29f5009be30c444bb04dd2afb91d2b34e9dbd734cb920c4af79e1b3020900000002e49593ff00 | ||
1 output(s) for total of 34.717797907585 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8199f6f1562455dd2ea7c8cff65eaedc948e125797500373060ef521087ca8a3 | 34.717797907585 | 8632 of 0 | <47> |
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": 7060,
"vin": [ {
"gen": {
"height": 7000
}
}
],
"vout": [ {
"amount": 34717797907585,
"target": {
"tagged_key": {
"key": "8199f6f1562455dd2ea7c8cff65eaedc948e125797500373060ef521087ca8a3",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 228, 25, 125, 77, 194, 159, 80, 9, 190, 48, 196, 68, 187, 4, 221, 42, 251, 145, 210, 179, 78, 157, 189, 115, 76, 185, 32, 196, 175, 121, 225, 179, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}