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: dba85792b338eceda29841e946cf891ea51d93278fd3b2a07f47e3f795ea170a
Tx prefix hash: 9164145e403e73673e7bef46e15f2bb1bb7ab342aa54fceecc077758c49011fb
Tx public key: 555063ea08496c9e16a592e78aa6d519b9352b6c69b5bbc85ea67e23ec2d67d7
| Timestamp: 1779928116 | Timestamp [UTC]: 2026-05-28 00:28:36 | Age [y:d:h:m:s]: 00:012:01:07:21 |
| Block: 3389 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4497 | RingCT/type: yes/0 |
| Extra: 01555063ea08496c9e16a592e78aa6d519b9352b6c69b5bbc85ea67e23ec2d67d702090000000426697be300 | ||
1 output(s) for total of 34.961954489236 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff2abc8661374dd05a0df43238b111032108ab21ec1e42cca3725578681e98b2 | 34.961954489236 | 4094 of 0 | <4c> |
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": 3449,
"vin": [ {
"gen": {
"height": 3389
}
}
],
"vout": [ {
"amount": 34961954489236,
"target": {
"tagged_key": {
"key": "ff2abc8661374dd05a0df43238b111032108ab21ec1e42cca3725578681e98b2",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 85, 80, 99, 234, 8, 73, 108, 158, 22, 165, 146, 231, 138, 166, 213, 25, 185, 53, 43, 108, 105, 181, 187, 200, 94, 166, 126, 35, 236, 45, 103, 215, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}