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: 8116454b295f46d22ff8f4836d3d0fa8b88368679ce9a89cb625db28cb9e0f02
Tx prefix hash: 5e1fdcaddf3283d237cfbfc37ff2fb40b8a23fb426052a269d0efa123baf292c
Tx public key: 78aa73052cb2384aeb4e851143538751655d2d67eba88e3717f487dfe84a8344
| Timestamp: 1780798783 | Timestamp [UTC]: 2026-06-07 02:19:43 | Age [y:d:h:m:s]: 00:001:23:16:14 |
| Block: 6800 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1086 | RingCT/type: yes/0 |
| Extra: 0178aa73052cb2384aeb4e851143538751655d2d67eba88e3717f487dfe84a8344020900000001e49593ff00 | ||
1 output(s) for total of 34.731044235468 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1a009a778c3c9ea56db95f3bbecc94c868b4d787dbda757514c65c44272d8370 | 34.731044235468 | 8398 of 0 | <1b> |
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": 6860,
"vin": [ {
"gen": {
"height": 6800
}
}
],
"vout": [ {
"amount": 34731044235468,
"target": {
"tagged_key": {
"key": "1a009a778c3c9ea56db95f3bbecc94c868b4d787dbda757514c65c44272d8370",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 120, 170, 115, 5, 44, 178, 56, 74, 235, 78, 133, 17, 67, 83, 135, 81, 101, 93, 45, 103, 235, 168, 142, 55, 23, 244, 135, 223, 232, 74, 131, 68, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}