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: af7d17bd333dfa32618e45a65e2a92928dbd0f1e1b267d16e68b1ffc09d59991
Tx prefix hash: d633a75e17b6a49f1d38b549d03848f6fdf0219addfdeae29dee9e4831c6709a
Tx public key: 10618a6a65e4ef5d1fb2b54ce3fb045c65e1b07e610cb5b9ce764dca0ba5ac41
| Timestamp: 1779444558 | Timestamp [UTC]: 2026-05-22 10:09:18 | Age [y:d:h:m:s]: 00:017:16:40:30 |
| Block: 257 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7663 | RingCT/type: yes/0 |
| Extra: 0110618a6a65e4ef5d1fb2b54ce3fb045c65e1b07e610cb5b9ce764dca0ba5ac410209000000014438f87f00 | ||
1 output(s) for total of 35.167196397007 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8a61d6ba9462f9b19c1668d0fbe398fb9ff8ffcb1566ab0b16c37c6f4deecefe | 35.167196397007 | 253 of 0 | <ce> |
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": 317,
"vin": [ {
"gen": {
"height": 257
}
}
],
"vout": [ {
"amount": 35167196397007,
"target": {
"tagged_key": {
"key": "8a61d6ba9462f9b19c1668d0fbe398fb9ff8ffcb1566ab0b16c37c6f4deecefe",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 16, 97, 138, 106, 101, 228, 239, 93, 31, 178, 181, 76, 227, 251, 4, 92, 101, 225, 176, 126, 97, 12, 181, 185, 206, 118, 77, 202, 11, 165, 172, 65, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}