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: f30a62d0275fe65fe22192f7eed67816d89ca346d20fd0d9b56e6db9e3255bdb
Tx prefix hash: 6419e5bff42687d27a638a22faf08cb920b9912eecc2f662d3943c0b9fb29faf
Tx public key: 21fc9d38632d858d7dbc989a49bc024a2716dabba3999ae4be21d5e50d1e1c4a
| Timestamp: 1780754757 | Timestamp [UTC]: 2026-06-06 14:05:57 | Age [y:d:h:m:s]: 00:002:11:30:00 |
| Block: 6519 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1367 | RingCT/type: yes/0 |
| Extra: 0121fc9d38632d858d7dbc989a49bc024a2716dabba3999ae4be21d5e50d1e1c4a020900000001e49593ff00 | ||
1 output(s) for total of 34.777794265451 HMNY
| stealth address | amount | amount idx | tag |
| 00: c1ed67d1e2e9c184f2a9a343a8bfd5e8919d98cc120c643716489c97fb4a113d | 34.777794265451 | 8016 of 0 | <0c> |
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": 6579,
"vin": [ {
"gen": {
"height": 6519
}
}
],
"vout": [ {
"amount": 34777794265451,
"target": {
"tagged_key": {
"key": "c1ed67d1e2e9c184f2a9a343a8bfd5e8919d98cc120c643716489c97fb4a113d",
"view_tag": "0c"
}
}
}
],
"extra": [ 1, 33, 252, 157, 56, 99, 45, 133, 141, 125, 188, 152, 154, 73, 188, 2, 74, 39, 22, 218, 187, 163, 153, 154, 228, 190, 33, 213, 229, 13, 30, 28, 74, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}