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: 25045a4751f57b410db238e7c1025b2d123ca54a55350d4c146e7c7c9622f0f3
Tx prefix hash: f68f83c8271ac54058494d99d3c2c3f289cf45d2e277055337fbe2a72f426718
Tx public key: 22fabba7e983c56c2d4404f2485a742b07d17267031de7b44aa19da464cc0f9f
| Timestamp: 1779861400 | Timestamp [UTC]: 2026-05-27 05:56:40 | Age [y:d:h:m:s]: 00:012:17:22:13 |
| Block: 2691 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5195 | RingCT/type: yes/0 |
| Extra: 0122fabba7e983c56c2d4404f2485a742b07d17267031de7b44aa19da464cc0f9f02090000000626697be300 | ||
1 output(s) for total of 35.004311392883 HMNY
| stealth address | amount | amount idx | tag |
| 00: afcabde4e5e405c4da80bfefa3beb6841a1c59a8173835168f2a3dca4b49bb5e | 35.004311392883 | 3173 of 0 | <44> |
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": 2751,
"vin": [ {
"gen": {
"height": 2691
}
}
],
"vout": [ {
"amount": 35004311392883,
"target": {
"tagged_key": {
"key": "afcabde4e5e405c4da80bfefa3beb6841a1c59a8173835168f2a3dca4b49bb5e",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 34, 250, 187, 167, 233, 131, 197, 108, 45, 68, 4, 242, 72, 90, 116, 43, 7, 209, 114, 103, 3, 29, 231, 180, 74, 161, 157, 164, 100, 204, 15, 159, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}