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: 72f4c24b047e9cc561f033dc440e29c9349dee1964997fa848b75918ed5eac30
Tx prefix hash: 81c7d0555b390f2e9eef2ac75c53e5c62dba7b03a025b9580bdf9e802390bc01
Tx public key: 3f4964d414e2fbb309b7409d79a8cfa6c2c0d4660298977a87ab7667ab401abb
| Timestamp: 1780034248 | Timestamp [UTC]: 2026-05-29 05:57:28 | Age [y:d:h:m:s]: 00:010:22:35:34 |
| Block: 4226 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3803 | RingCT/type: yes/0 |
| Extra: 013f4964d414e2fbb309b7409d79a8cfa6c2c0d4660298977a87ab7667ab401abb02090000000326697be300 | ||
1 output(s) for total of 34.901976247684 HMNY
| stealth address | amount | amount idx | tag |
| 00: bd29cad142197d097836f6d5602df4fccfb13be67a65e45d4f0c353ba20cb437 | 34.901976247684 | 5268 of 0 | <44> |
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": 4286,
"vin": [ {
"gen": {
"height": 4226
}
}
],
"vout": [ {
"amount": 34901976247684,
"target": {
"tagged_key": {
"key": "bd29cad142197d097836f6d5602df4fccfb13be67a65e45d4f0c353ba20cb437",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 63, 73, 100, 212, 20, 226, 251, 179, 9, 183, 64, 157, 121, 168, 207, 166, 194, 192, 212, 102, 2, 152, 151, 122, 135, 171, 118, 103, 171, 64, 26, 187, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}