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: f38e67fe78775a7a8734638fb2dbf5e805617e32e3d4e362c9e1b4f540b9d10d
Tx prefix hash: 65a08552e29ef1092d14b4a66ff4c96f8b301bd127fda3bcedeedaa9891c330a
Tx public key: 20f56185138e46938667e86753dbbfb4bdb22ebec980929f444cff102f5c2808
| Timestamp: 1780686374 | Timestamp [UTC]: 2026-06-05 19:06:14 | Age [y:d:h:m:s]: 00:003:22:02:49 |
| Block: 5425 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3309 | RingCT/type: yes/0 |
| Extra: 0120f56185138e46938667e86753dbbfb4bdb22ebec980929f444cff102f5c2808020900000001e49593ff00 | ||
1 output(s) for total of 34.822249656431 HMNY
| stealth address | amount | amount idx | tag |
| 00: a1d1302bd4e64219e57527ce7addeaa6499909b3c8b061a99678e9ed664c06f4 | 34.822249656431 | 6862 of 0 | <05> |
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": 5485,
"vin": [ {
"gen": {
"height": 5425
}
}
],
"vout": [ {
"amount": 34822249656431,
"target": {
"tagged_key": {
"key": "a1d1302bd4e64219e57527ce7addeaa6499909b3c8b061a99678e9ed664c06f4",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 32, 245, 97, 133, 19, 142, 70, 147, 134, 103, 232, 103, 83, 219, 191, 180, 189, 178, 46, 190, 201, 128, 146, 159, 68, 76, 255, 16, 47, 92, 40, 8, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}