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: add7ccd514b147846b9914c90e03461ed05105b2741ec003612050903ceba6d7
Tx prefix hash: dbdd5594133ae3ea64aa959c64927e32e70ec3629195873e3f1a7502e429fd15
Tx public key: 48d3d0e5f15f41d24a747f38b1b6b9664b46964c2d90e5f7112590aae168f10b
| Timestamp: 1780995409 | Timestamp [UTC]: 2026-06-09 08:56:49 | Age [y:d:h:m:s]: 00:000:04:40:47 |
| Block: 8320 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 278 | RingCT/type: yes/0 |
| Extra: 0148d3d0e5f15f41d24a747f38b1b6b9664b46964c2d90e5f7112590aae168f10b020900000002e49593ff00 | ||
1 output(s) for total of 34.630498760412 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84d4960bc5e147f6a964d2c4bc4e4ca3f9efa9a2ecae2c0ff8eb55796ad187c7 | 34.630498760412 | 10292 of 0 | <5c> |
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": 8380,
"vin": [ {
"gen": {
"height": 8320
}
}
],
"vout": [ {
"amount": 34630498760412,
"target": {
"tagged_key": {
"key": "84d4960bc5e147f6a964d2c4bc4e4ca3f9efa9a2ecae2c0ff8eb55796ad187c7",
"view_tag": "5c"
}
}
}
],
"extra": [ 1, 72, 211, 208, 229, 241, 95, 65, 210, 74, 116, 127, 56, 177, 182, 185, 102, 75, 70, 150, 76, 45, 144, 229, 247, 17, 37, 144, 170, 225, 104, 241, 11, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}