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: 7878bb2097404b74fd4a4648932130b7116897f35d326c0ccba6990568902a54
Tx prefix hash: f252a203fb7cb738255fa8efd342ff895f5a03d36b630ce7bf14cb851d26690e
Tx public key: daf974fe53fe567991042c1ddf470e70326324e770b8b3e6f02ab184be8d0ada
| Timestamp: 1779453849 | Timestamp [UTC]: 2026-05-22 12:44:09 | Age [y:d:h:m:s]: 00:017:10:34:44 |
| Block: 358 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7528 | RingCT/type: yes/0 |
| Extra: 01daf974fe53fe567991042c1ddf470e70326324e770b8b3e6f02ab184be8d0ada02090000000193369e7d00 | ||
1 output(s) for total of 35.160422356550 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30c3350f5e8ea1554c05f12341bacaea562fb6fe311e7b02facbe1ab23c9d50b | 35.160422356550 | 354 of 0 | <a5> |
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": 418,
"vin": [ {
"gen": {
"height": 358
}
}
],
"vout": [ {
"amount": 35160422356550,
"target": {
"tagged_key": {
"key": "30c3350f5e8ea1554c05f12341bacaea562fb6fe311e7b02facbe1ab23c9d50b",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 218, 249, 116, 254, 83, 254, 86, 121, 145, 4, 44, 29, 223, 71, 14, 112, 50, 99, 36, 231, 112, 184, 179, 230, 240, 42, 177, 132, 190, 141, 10, 218, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}