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: d5f42d06c83e855e739b478dae17dd3cbf86bff5ebbf858d87d57fca248fa6f0
Tx prefix hash: cfe9683d1888eba1596bfa8b1a4ac192d9b1df2503d8b3a42d7c79a6d7dc825f
Tx public key: c43229fda92a3b838484cf10993c37ea33da86a76f2ea7e4ac45edb4c5aa6f13
| Timestamp: 1779805120 | Timestamp [UTC]: 2026-05-26 14:18:40 | Age [y:d:h:m:s]: 00:014:02:50:23 |
| Block: 2343 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6392 | RingCT/type: yes/0 |
| Extra: 01c43229fda92a3b838484cf10993c37ea33da86a76f2ea7e4ac45edb4c5aa6f1302090000000226697be300 | ||
1 output(s) for total of 35.038136295819 HMNY
| stealth address | amount | amount idx | tag |
| 00: 78819c52d01ea825fa367c6b33b37357b80cdc42bd28285f1600c5ffd8457fa4 | 35.038136295819 | 2741 of 0 | <20> |
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": 2403,
"vin": [ {
"gen": {
"height": 2343
}
}
],
"vout": [ {
"amount": 35038136295819,
"target": {
"tagged_key": {
"key": "78819c52d01ea825fa367c6b33b37357b80cdc42bd28285f1600c5ffd8457fa4",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 196, 50, 41, 253, 169, 42, 59, 131, 132, 132, 207, 16, 153, 60, 55, 234, 51, 218, 134, 167, 111, 46, 167, 228, 172, 69, 237, 180, 197, 170, 111, 19, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}