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: 508b9660676fe051050b57ee82cf93cb38004ed12c4ad59d6ab96a70d97f477b
Tx prefix hash: dcde8abd9809d2825e9149732c44b2054fbca07a8f43bd1fa256a7c5b90a20b7
Tx public key: 46dc0c4757918b8e893ebfc88a58f50531ae3a0740fbfe6a8d0e7aebc98df9bc
| Timestamp: 1779717883 | Timestamp [UTC]: 2026-05-25 14:04:43 | Age [y:d:h:m:s]: 00:014:13:46:15 |
| Block: 1694 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6259 | RingCT/type: yes/0 |
| Extra: 0146dc0c4757918b8e893ebfc88a58f50531ae3a0740fbfe6a8d0e7aebc98df9bc020900000002ba6d17be00 | ||
1 output(s) for total of 35.070939916834 HMNY
| stealth address | amount | amount idx | tag |
| 00: f878a0b78f4fc1900f13bcdfb115dab818a1491e1b16917975f9cfff45b41de5 | 35.070939916834 | 1863 of 0 | <4f> |
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": 1754,
"vin": [ {
"gen": {
"height": 1694
}
}
],
"vout": [ {
"amount": 35070939916834,
"target": {
"tagged_key": {
"key": "f878a0b78f4fc1900f13bcdfb115dab818a1491e1b16917975f9cfff45b41de5",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 70, 220, 12, 71, 87, 145, 139, 142, 137, 62, 191, 200, 138, 88, 245, 5, 49, 174, 58, 7, 64, 251, 254, 106, 141, 14, 122, 235, 201, 141, 249, 188, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}