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: 870b9eb66f5d4c5bc992be8d4a2b29ea746928910d968d8b0f53b04f17f6f53d
Tx prefix hash: d58a93be2e10b2aff9eaef4fa0786e8762b743ab1292f63f6506da7bf8ea6f3c
Tx public key: 15315d3b20e9031594b8d7bf17337bdad9a3bd85864b04f2834470f3344b2c19
| Timestamp: 1780692802 | Timestamp [UTC]: 2026-06-05 20:53:22 | Age [y:d:h:m:s]: 00:007:14:08:54 |
| Block: 5819 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2926 | RingCT/type: yes/0 |
| Extra: 0115315d3b20e9031594b8d7bf17337bdad9a3bd85864b04f2834470f3344b2c19020900000001e49593ff00 | ||
1 output(s) for total of 34.796090702793 HMNY
| stealth address | amount | amount idx | tag |
| 00: d82a4eba64307e87f038a52c7ed637f63b64539d3b741ff04f51b93a55dfbda0 | 34.796090702793 | 7276 of 0 | <b8> |
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": 5879,
"vin": [ {
"gen": {
"height": 5819
}
}
],
"vout": [ {
"amount": 34796090702793,
"target": {
"tagged_key": {
"key": "d82a4eba64307e87f038a52c7ed637f63b64539d3b741ff04f51b93a55dfbda0",
"view_tag": "b8"
}
}
}
],
"extra": [ 1, 21, 49, 93, 59, 32, 233, 3, 21, 148, 184, 215, 191, 23, 51, 123, 218, 217, 163, 189, 133, 134, 75, 4, 242, 131, 68, 112, 243, 52, 75, 44, 25, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}