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: 9347a755441aab357fd78a31c6596f64c7f6c65b2770c1be989187fed2076ef6
Tx prefix hash: 1360daaa8d1aacf038edf22ce6b9d253900790cf33bad0719d312e3494454512
Tx public key: 6685e26b21c97a92add00c7c402692d83b582b3b0fa33c39e3b80efba175a601
| Timestamp: 1779784405 | Timestamp [UTC]: 2026-05-26 08:33:25 | Age [y:d:h:m:s]: 00:013:17:02:32 |
| Block: 2144 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5742 | RingCT/type: yes/0 |
| Extra: 016685e26b21c97a92add00c7c402692d83b582b3b0fa33c39e3b80efba175a60102090000000226697be300 | ||
1 output(s) for total of 35.040851173488 HMNY
| stealth address | amount | amount idx | tag |
| 00: b33ea5a91dac7a178a3bea7aac24e20775ada24375bd2b46a7eb657ecee426dc | 35.040851173488 | 2474 of 0 | <8e> |
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": 2204,
"vin": [ {
"gen": {
"height": 2144
}
}
],
"vout": [ {
"amount": 35040851173488,
"target": {
"tagged_key": {
"key": "b33ea5a91dac7a178a3bea7aac24e20775ada24375bd2b46a7eb657ecee426dc",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 102, 133, 226, 107, 33, 201, 122, 146, 173, 208, 12, 124, 64, 38, 146, 216, 59, 88, 43, 59, 15, 163, 60, 57, 227, 184, 14, 251, 161, 117, 166, 1, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}