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: d9ef75589c3e1b04658a02b76ea92f4b24ff6237c4b98aa0adee747fc2e221ca
Tx prefix hash: e90d8e06e765f80955d81ddac9321f133b7574462428d46019754cd70077643d
Tx public key: 881bf1660e3eefa87acf95c7311b57f351028de4e14e66353001d7251b3f28af
| Timestamp: 1780061070 | Timestamp [UTC]: 2026-05-29 13:24:30 | Age [y:d:h:m:s]: 00:010:09:00:19 |
| Block: 4523 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3363 | RingCT/type: yes/0 |
| Extra: 01881bf1660e3eefa87acf95c7311b57f351028de4e14e66353001d7251b3f28af02090000000226697be300 | ||
1 output(s) for total of 34.882210467554 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff4c19f985f518f374676f1d16681479f2531015476506648be78672fefd6147 | 34.882210467554 | 5671 of 0 | <b7> |
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": 4583,
"vin": [ {
"gen": {
"height": 4523
}
}
],
"vout": [ {
"amount": 34882210467554,
"target": {
"tagged_key": {
"key": "ff4c19f985f518f374676f1d16681479f2531015476506648be78672fefd6147",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 136, 27, 241, 102, 14, 62, 239, 168, 122, 207, 149, 199, 49, 27, 87, 243, 81, 2, 141, 228, 225, 78, 102, 53, 48, 1, 215, 37, 27, 63, 40, 175, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}