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: 1e9bafc5554e1077c92c353d6006d846c84de8ccdea4b19cbed59ac5884c7b3f
Tx prefix hash: f393addb2bfd37760c705d79c3cf65099eea35df2b26ad19e763d13e2bfa1dab
Tx public key: 8ab68ee4ddc936a3d33a81384c5095d4e79f57cf73443ee891ea8b3ea6552dfb
| Timestamp: 1780862534 | Timestamp [UTC]: 2026-06-07 20:02:14 | Age [y:d:h:m:s]: 00:001:01:09:53 |
| Block: 7632 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 254 | RingCT/type: yes/0 |
| Extra: 018ab68ee4ddc936a3d33a81384c5095d4e79f57cf73443ee891ea8b3ea6552dfb020900000001e49593ff00 | ||
1 output(s) for total of 34.680999508892 HMNY
| stealth address | amount | amount idx | tag |
| 00: 16c5272cd24e58a90316d514c20852d5649e90f6a6f8f92a5f3c79c7e5365f68 | 34.680999508892 | 9432 of 0 | <bc> |
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": 7692,
"vin": [ {
"gen": {
"height": 7632
}
}
],
"vout": [ {
"amount": 34680999508892,
"target": {
"tagged_key": {
"key": "16c5272cd24e58a90316d514c20852d5649e90f6a6f8f92a5f3c79c7e5365f68",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 138, 182, 142, 228, 221, 201, 54, 163, 211, 58, 129, 56, 76, 80, 149, 212, 231, 159, 87, 207, 115, 68, 62, 232, 145, 234, 139, 62, 166, 85, 45, 251, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}