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: 52c19e858bd51b7c39b70771ff5f41dddc308cd8c6f029847b3133b73a275590
Tx prefix hash: 4b1c91c91fd9a7d1a3d2bc17c1097629a0d9a3c7de3985f6e13fc31068716ffc
Tx public key: 91b3273c04201184cdbccec8cef3baad153d57a7e089f8448895cab3158abc83
| Timestamp: 1780827088 | Timestamp [UTC]: 2026-06-07 10:11:28 | Age [y:d:h:m:s]: 00:001:13:07:25 |
| Block: 7281 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 605 | RingCT/type: yes/0 |
| Extra: 0191b3273c04201184cdbccec8cef3baad153d57a7e089f8448895cab3158abc83020900000001e49593ff00 | ||
1 output(s) for total of 34.699195352080 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a25f4939b5ab0a4108a29e418a08b263000b74ab816a9f58ceafaf2a3b639f2 | 34.699195352080 | 8965 of 0 | <9a> |
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": 7341,
"vin": [ {
"gen": {
"height": 7281
}
}
],
"vout": [ {
"amount": 34699195352080,
"target": {
"tagged_key": {
"key": "0a25f4939b5ab0a4108a29e418a08b263000b74ab816a9f58ceafaf2a3b639f2",
"view_tag": "9a"
}
}
}
],
"extra": [ 1, 145, 179, 39, 60, 4, 32, 17, 132, 205, 188, 206, 200, 206, 243, 186, 173, 21, 61, 87, 167, 224, 137, 248, 68, 136, 149, 202, 179, 21, 138, 188, 131, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}