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: 7ce152e36da32db400209f1960c2ff106184b51b996658f872379558011c81bf
Tx prefix hash: f6537a4e6c34922f50d56947ca0eecb526317db9a00f670a9bf51a8a3e1f3b8c
Tx public key: f99b7d0300b7a7a45e6510164b4a8e4a41a18382389f11fe781c35a90d94d14a
| Timestamp: 1780315031 | Timestamp [UTC]: 2026-06-01 11:57:11 | Age [y:d:h:m:s]: 00:007:14:52:37 |
| Block: 4996 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2903 | RingCT/type: yes/0 |
| Extra: 01f99b7d0300b7a7a45e6510164b4a8e4a41a18382389f11fe781c35a90d94d14a02090000000126697be300 | ||
1 output(s) for total of 34.850754739251 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0718eaa2a3d9b775e441e0308b3222c9f73816996d0d4f81a7ffee8e7df2db2b | 34.850754739251 | 6363 of 0 | <f4> |
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": 5056,
"vin": [ {
"gen": {
"height": 4996
}
}
],
"vout": [ {
"amount": 34850754739251,
"target": {
"tagged_key": {
"key": "0718eaa2a3d9b775e441e0308b3222c9f73816996d0d4f81a7ffee8e7df2db2b",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 249, 155, 125, 3, 0, 183, 167, 164, 94, 101, 16, 22, 75, 74, 142, 74, 65, 161, 131, 130, 56, 159, 17, 254, 120, 28, 53, 169, 13, 148, 209, 74, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}