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: 31c7e4c4f601a32b1c0f03ae5836f057bd9068c5eb58e297de24db5f1283f33e
Tx prefix hash: 9b26acddcb6f8e190ea1b36edeb99f04547c51253f466fb3515279d90103574b
Tx public key: 28f34750a3b0c1a16dbe66e24780aa4f482a10a072edec7bb44513bebfd98729
| Timestamp: 1780859480 | Timestamp [UTC]: 2026-06-07 19:11:20 | Age [y:d:h:m:s]: 00:001:02:00:47 |
| Block: 7606 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 280 | RingCT/type: yes/0 |
| Extra: 0128f34750a3b0c1a16dbe66e24780aa4f482a10a072edec7bb44513bebfd98729020900000002e49593ff00 | ||
1 output(s) for total of 34.677692371570 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2391006d48f3e41e0609ecfc971cb18ca18051445e2f3585783f7edfa63dbe32 | 34.677692371570 | 9398 of 0 | <14> |
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": 7666,
"vin": [ {
"gen": {
"height": 7606
}
}
],
"vout": [ {
"amount": 34677692371570,
"target": {
"tagged_key": {
"key": "2391006d48f3e41e0609ecfc971cb18ca18051445e2f3585783f7edfa63dbe32",
"view_tag": "14"
}
}
}
],
"extra": [ 1, 40, 243, 71, 80, 163, 176, 193, 161, 109, 190, 102, 226, 71, 128, 170, 79, 72, 42, 16, 160, 114, 237, 236, 123, 180, 69, 19, 190, 191, 217, 135, 41, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}