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: 5502549ca930df63a1e80b1613f8c867b185c3d75068908bb1b13f8f7ddccdf8
Tx prefix hash: c9a63992c41195f0a5c10c626e06d6111b9ecbe031ba3130d86edabc68aa0b00
Tx public key: f319f0fa7dc46ce4cce2f85dbd2a16ff0aee1c524e27fd14ce607d4e4beb43f1
| Timestamp: 1780865343 | Timestamp [UTC]: 2026-06-07 20:49:03 | Age [y:d:h:m:s]: 00:001:03:57:44 |
| Block: 7658 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 228 | RingCT/type: yes/0 |
| Extra: 01f319f0fa7dc46ce4cce2f85dbd2a16ff0aee1c524e27fd14ce607d4e4beb43f1020900000002e49593ff00 | ||
1 output(s) for total of 34.674253131493 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5549057c65274105343b65f53985421c46db4d3b31cd5ccc0df913a67d8a18fa | 34.674253131493 | 9468 of 0 | <cf> |
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": 7718,
"vin": [ {
"gen": {
"height": 7658
}
}
],
"vout": [ {
"amount": 34674253131493,
"target": {
"tagged_key": {
"key": "5549057c65274105343b65f53985421c46db4d3b31cd5ccc0df913a67d8a18fa",
"view_tag": "cf"
}
}
}
],
"extra": [ 1, 243, 25, 240, 250, 125, 196, 108, 228, 204, 226, 248, 93, 189, 42, 22, 255, 10, 238, 28, 82, 78, 39, 253, 20, 206, 96, 125, 78, 75, 235, 67, 241, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}