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: 1717d82c268821f5d735fa407bb134f28e3690cd2f6930783866096783d2ec2e
Tx prefix hash: c64433ccfa3e12dbb348985c636afe0649cc92854ff3ebdc8773c73809dbb3f6
Tx public key: 4d7dd14ae7a76b0b608645123459832f0374e0e4fa734ad5d4e37d371a3bfc48
| Timestamp: 1779773847 | Timestamp [UTC]: 2026-05-26 05:37:27 | Age [y:d:h:m:s]: 00:013:19:58:30 |
| Block: 2050 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5836 | RingCT/type: yes/0 |
| Extra: 014d7dd14ae7a76b0b608645123459832f0374e0e4fa734ad5d4e37d371a3bfc4802090000000226697be300 | ||
1 output(s) for total of 35.047134243952 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4cea4a44043df8de2b125e1a0d992dbf50f3ff1d850a181466461ca0959da7c7 | 35.047134243952 | 2344 of 0 | <6f> |
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": 2110,
"vin": [ {
"gen": {
"height": 2050
}
}
],
"vout": [ {
"amount": 35047134243952,
"target": {
"tagged_key": {
"key": "4cea4a44043df8de2b125e1a0d992dbf50f3ff1d850a181466461ca0959da7c7",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 77, 125, 209, 74, 231, 167, 107, 11, 96, 134, 69, 18, 52, 89, 131, 47, 3, 116, 224, 228, 250, 115, 74, 213, 212, 227, 125, 55, 26, 59, 252, 72, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}