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: 69e19c44cb2050980cf98dc5a5e8f7e50764793fc37156569307d41383225679
Tx prefix hash: 78acfeacb41feb9ba3f09f2bcb5c9f6aa9d3be7ab05a03098166c642568c4a62
Tx public key: 11c9b7a97f721adb4f0b4d3a810247552d8953c6a9934845c92cc8a0bd1f19eb
| Timestamp: 1780799117 | Timestamp [UTC]: 2026-06-07 02:25:17 | Age [y:d:h:m:s]: 00:001:23:10:40 |
| Block: 6808 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1078 | RingCT/type: yes/0 |
| Extra: 0111c9b7a97f721adb4f0b4d3a810247552d8953c6a9934845c92cc8a0bd1f19eb020900000001e49593ff00 | ||
1 output(s) for total of 34.730514285328 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4a2419fe87d3a1790fc60c8df0de25bcce0f082a0f6c53431e4875b23efc7138 | 34.730514285328 | 8406 of 0 | <6e> |
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": 6868,
"vin": [ {
"gen": {
"height": 6808
}
}
],
"vout": [ {
"amount": 34730514285328,
"target": {
"tagged_key": {
"key": "4a2419fe87d3a1790fc60c8df0de25bcce0f082a0f6c53431e4875b23efc7138",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 17, 201, 183, 169, 127, 114, 26, 219, 79, 11, 77, 58, 129, 2, 71, 85, 45, 137, 83, 198, 169, 147, 72, 69, 201, 44, 200, 160, 189, 31, 25, 235, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}