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: 54180ddd2f3c97d694d62d0b801167e2f49af873749658d500e4d672ee27bf26
Tx prefix hash: 26a6ec57ea34705fd18a3c11045f816bd6da191be86409a2c3563c3204f7a49b
Tx public key: 1227ea06b77f3f63dacb5684c1e6b3bcd29f8c984ef87d3215642e8d1326e33e
| Timestamp: 1779719543 | Timestamp [UTC]: 2026-05-25 14:32:23 | Age [y:d:h:m:s]: 00:014:11:03:34 |
| Block: 1724 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6162 | RingCT/type: yes/0 |
| Extra: 011227ea06b77f3f63dacb5684c1e6b3bcd29f8c984ef87d3215642e8d1326e33e020900000003ba6d17be00 | ||
1 output(s) for total of 35.068933197055 HMNY
| stealth address | amount | amount idx | tag |
| 00: c72f149bb1b4bc916dc4ad5148adcc24d0a88468cf1b92ee062b1e78b25491c9 | 35.068933197055 | 1900 of 0 | <3b> |
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": 1784,
"vin": [ {
"gen": {
"height": 1724
}
}
],
"vout": [ {
"amount": 35068933197055,
"target": {
"tagged_key": {
"key": "c72f149bb1b4bc916dc4ad5148adcc24d0a88468cf1b92ee062b1e78b25491c9",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 18, 39, 234, 6, 183, 127, 63, 99, 218, 203, 86, 132, 193, 230, 179, 188, 210, 159, 140, 152, 78, 248, 125, 50, 21, 100, 46, 141, 19, 38, 227, 62, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}