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: 18a1969a89f9b0a5dedc772525405a7b6769b8dcfbe94f6718cdc11d10021c09
Tx prefix hash: 5a0b450f8c079e9f2f4808b982eb2d4649743ca6bf690296bf0a683bb951e712
Tx public key: 7773e139bee0abdcc9614f61e062f7e8b8e60e1422e744a8c2a8ff862f5e465d
| Timestamp: 1780323165 | Timestamp [UTC]: 2026-06-01 14:12:45 | Age [y:d:h:m:s]: 00:007:10:34:02 |
| Block: 5067 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2819 | RingCT/type: yes/0 |
| Extra: 017773e139bee0abdcc9614f61e062f7e8b8e60e1422e744a8c2a8ff862f5e465d02090000005626697be300 | ||
1 output(s) for total of 34.846035504003 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6fbe3e2c6f292e69c207437924026541e97aa5ff35d5e7f5130a5b57c4447468 | 34.846035504003 | 6442 of 0 | <ac> |
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": 5127,
"vin": [ {
"gen": {
"height": 5067
}
}
],
"vout": [ {
"amount": 34846035504003,
"target": {
"tagged_key": {
"key": "6fbe3e2c6f292e69c207437924026541e97aa5ff35d5e7f5130a5b57c4447468",
"view_tag": "ac"
}
}
}
],
"extra": [ 1, 119, 115, 225, 57, 190, 224, 171, 220, 201, 97, 79, 97, 224, 98, 247, 232, 184, 230, 14, 20, 34, 231, 68, 168, 194, 168, 255, 134, 47, 94, 70, 93, 2, 9, 0, 0, 0, 86, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}