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: 8b86bd388a588cfd5724c1951fc9f4dc5122828318b76f7723d7e6140f2ffe91
Tx prefix hash: ca5b46d5aee1630255b21beecf98664d6388044d8d10ffca1c169a1d4a7bed6e
Tx public key: bbdaca0672c4ac8cb061c129d1904dac14969ec431ff91e8dc69e9b9dedc6a16
| Timestamp: 1779934261 | Timestamp [UTC]: 2026-05-28 02:11:01 | Age [y:d:h:m:s]: 00:012:14:58:02 |
| Block: 3425 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5308 | RingCT/type: yes/0 |
| Extra: 01bbdaca0672c4ac8cb061c129d1904dac14969ec431ff91e8dc69e9b9dedc6a1602090000000126697be300 | ||
1 output(s) for total of 34.955339811835 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6714129e16c9e2fb67de3387423ac4ef71e57c8926d09e2a362aec23dcd7dc73 | 34.955339811835 | 4140 of 0 | <76> |
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": 3485,
"vin": [ {
"gen": {
"height": 3425
}
}
],
"vout": [ {
"amount": 34955339811835,
"target": {
"tagged_key": {
"key": "6714129e16c9e2fb67de3387423ac4ef71e57c8926d09e2a362aec23dcd7dc73",
"view_tag": "76"
}
}
}
],
"extra": [ 1, 187, 218, 202, 6, 114, 196, 172, 140, 176, 97, 193, 41, 209, 144, 77, 172, 20, 150, 158, 196, 49, 255, 145, 232, 220, 105, 233, 185, 222, 220, 106, 22, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}