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: f1fa3e38d490c3eea444314b6b3cbc2d861cb45d2b131e5b368a44a08a712f6f
Tx prefix hash: c718ad18faaac3cd78e2f6792c2722f0915604de8e216f55a841f14f47e3d814
Tx public key: 3081841422e34706403b05fedc75acd7497de1f8f56aa2b513e1e3cd02a37c5f
| Timestamp: 1780840064 | Timestamp [UTC]: 2026-06-07 13:47:44 | Age [y:d:h:m:s]: 00:002:03:21:19 |
| Block: 7455 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1280 | RingCT/type: yes/0 |
| Extra: 013081841422e34706403b05fedc75acd7497de1f8f56aa2b513e1e3cd02a37c5f020900000001e49593ff00 | ||
1 output(s) for total of 34.687681329304 HMNY
| stealth address | amount | amount idx | tag |
| 00: a8368dae30e99c9ba41a88b9cc09116c07a57092951cc03d7778a9db203d6d3d | 34.687681329304 | 9181 of 0 | <e5> |
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": 7515,
"vin": [ {
"gen": {
"height": 7455
}
}
],
"vout": [ {
"amount": 34687681329304,
"target": {
"tagged_key": {
"key": "a8368dae30e99c9ba41a88b9cc09116c07a57092951cc03d7778a9db203d6d3d",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 48, 129, 132, 20, 34, 227, 71, 6, 64, 59, 5, 254, 220, 117, 172, 215, 73, 125, 225, 248, 245, 106, 162, 181, 19, 225, 227, 205, 2, 163, 124, 95, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}