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: e6adb3593b5323924d9a8930c2e1a3f07ea211e986bd9bbfd9d7c03577a3528a
Tx prefix hash: 99189e888d01a307eb21b90241e898f1be69c9f8603ff7706721fd52fe336a70
Tx public key: 5348906f39f783fb2a0e962b7b8e113d4752c16aafac966a30d7484e37df2286
| Timestamp: 1780131252 | Timestamp [UTC]: 2026-05-30 08:54:12 | Age [y:d:h:m:s]: 00:015:23:25:23 |
| Block: 4938 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3807 | RingCT/type: yes/0 |
| Extra: 015348906f39f783fb2a0e962b7b8e113d4752c16aafac966a30d7484e37df228602090000000726697be300 | ||
1 output(s) for total of 34.854610363476 HMNY
| stealth address | amount | amount idx | tag |
| 00: 73714b04cc2cd731c5a0e7fd002a3816d1692a9478ecd6378c1a3e99f87f0a54 | 34.854610363476 | 6273 of 0 | <c3> |
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": 4998,
"vin": [ {
"gen": {
"height": 4938
}
}
],
"vout": [ {
"amount": 34854610363476,
"target": {
"tagged_key": {
"key": "73714b04cc2cd731c5a0e7fd002a3816d1692a9478ecd6378c1a3e99f87f0a54",
"view_tag": "c3"
}
}
}
],
"extra": [ 1, 83, 72, 144, 111, 57, 247, 131, 251, 42, 14, 150, 43, 123, 142, 17, 61, 71, 82, 193, 106, 175, 172, 150, 106, 48, 215, 72, 78, 55, 223, 34, 134, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}