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: f975c38c8909b94cb8254e7ef09e5d7dc76069736d5551d0e27453a19ab3bb4b
Tx prefix hash: 3ee31bf7a2d336af8b76d1a2e0caad4419e8619c8f832a98fdfa0543dd492f27
Tx public key: 986507f0769f27adee58011b513f9ab1492a32d15261444e289159f7679be33f
| Timestamp: 1779636341 | Timestamp [UTC]: 2026-05-24 15:25:41 | Age [y:d:h:m:s]: 00:015:10:10:16 |
| Block: 1108 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6778 | RingCT/type: yes/0 |
| Extra: 01986507f0769f27adee58011b513f9ab1492a32d15261444e289159f7679be33f020900000001ba6d17be00 | ||
1 output(s) for total of 35.110160879364 HMNY
| stealth address | amount | amount idx | tag |
| 00: 436373c247f5ca6efc975a89bf7f755d8f6dfe68bb6af0f0ad0c4806c865fdb4 | 35.110160879364 | 1248 of 0 | <96> |
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": 1168,
"vin": [ {
"gen": {
"height": 1108
}
}
],
"vout": [ {
"amount": 35110160879364,
"target": {
"tagged_key": {
"key": "436373c247f5ca6efc975a89bf7f755d8f6dfe68bb6af0f0ad0c4806c865fdb4",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 152, 101, 7, 240, 118, 159, 39, 173, 238, 88, 1, 27, 81, 63, 154, 177, 73, 42, 50, 209, 82, 97, 68, 78, 40, 145, 89, 247, 103, 155, 227, 63, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}