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: 58a501946af7adfea3b8b93696a04d73a27635a6a7a5b8baa0a27dbe35c31eb4
Tx prefix hash: b2ac773f1997df6fab446fae7a738ce93822d9dd7c016e4e614002fea78696cd
Tx public key: ccd3f63628ae172c4868e9b18ee4a3b0359a19d52b5cc666215acca54dbe03e4
| Timestamp: 1780996726 | Timestamp [UTC]: 2026-06-09 09:18:46 | Age [y:d:h:m:s]: 00:000:05:30:09 |
| Block: 8358 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 298 | RingCT/type: yes/0 |
| Extra: 01ccd3f63628ae172c4868e9b18ee4a3b0359a19d52b5cc666215acca54dbe03e4020900000001e49593ff00 | ||
1 output(s) for total of 34.627988856467 HMNY
| stealth address | amount | amount idx | tag |
| 00: 01475aeba9c0235417aee66b3705d9eeab6231eb0472011dd1e462a315f2bb84 | 34.627988856467 | 10334 of 0 | <ee> |
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": 8418,
"vin": [ {
"gen": {
"height": 8358
}
}
],
"vout": [ {
"amount": 34627988856467,
"target": {
"tagged_key": {
"key": "01475aeba9c0235417aee66b3705d9eeab6231eb0472011dd1e462a315f2bb84",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 204, 211, 246, 54, 40, 174, 23, 44, 72, 104, 233, 177, 142, 228, 163, 176, 53, 154, 25, 213, 43, 92, 198, 102, 33, 90, 204, 165, 77, 190, 3, 228, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}