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: 9f44143a0454265f2d1e13a47d041fc106e75e6c4c52d3f944b0c3e9386f7fc2
Tx prefix hash: 4241a670c6330929a80d18c815d7ff070bc9ecceab7f98ede9d9cf5363608df4
Tx public key: f09364e167794c63c60cb33bc6ba081cf7338c263b8402f493817ef626bc0fcd
| Timestamp: 1780067007 | Timestamp [UTC]: 2026-05-29 15:03:27 | Age [y:d:h:m:s]: 00:010:07:21:22 |
| Block: 4599 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3287 | RingCT/type: yes/0 |
| Extra: 01f09364e167794c63c60cb33bc6ba081cf7338c263b8402f493817ef626bc0fcd02090000000426697be300 | ||
1 output(s) for total of 34.877154356434 HMNY
| stealth address | amount | amount idx | tag |
| 00: cfa9c4a542f24d1df2b829514611a744ac9b1b0a181d848d5653ea17d3eb4087 | 34.877154356434 | 5773 of 0 | <89> |
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": 4659,
"vin": [ {
"gen": {
"height": 4599
}
}
],
"vout": [ {
"amount": 34877154356434,
"target": {
"tagged_key": {
"key": "cfa9c4a542f24d1df2b829514611a744ac9b1b0a181d848d5653ea17d3eb4087",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 240, 147, 100, 225, 103, 121, 76, 99, 198, 12, 179, 59, 198, 186, 8, 28, 247, 51, 140, 38, 59, 132, 2, 244, 147, 129, 126, 246, 38, 188, 15, 205, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}