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: 7decc4d3a303668fd80aa28b066fad50f692ac38cf63b3eaa3b2fcfd5128e882
Tx prefix hash: ca5b03147f4a165619061a25bcc40eb0a0bf6b5c7585c874e6bea1fdfd4b345e
Tx public key: 4505011b0be742972b8e45a91bd752d95b2b84078cb6e41b5756338ffb0a1872
| Timestamp: 1780822481 | Timestamp [UTC]: 2026-06-07 08:54:41 | Age [y:d:h:m:s]: 00:006:02:07:35 |
| Block: 7203 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1542 | RingCT/type: yes/0 |
| Extra: 014505011b0be742972b8e45a91bd752d95b2b84078cb6e41b5756338ffb0a1872020900000001e49593ff00 | ||
1 output(s) for total of 34.704358051129 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0b623d728f481216780f7283fee77238a16d73340fd99cdf075bd723803f0cb8 | 34.704358051129 | 8871 of 0 | <d5> |
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": 7263,
"vin": [ {
"gen": {
"height": 7203
}
}
],
"vout": [ {
"amount": 34704358051129,
"target": {
"tagged_key": {
"key": "0b623d728f481216780f7283fee77238a16d73340fd99cdf075bd723803f0cb8",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 69, 5, 1, 27, 11, 231, 66, 151, 43, 142, 69, 169, 27, 215, 82, 217, 91, 43, 132, 7, 140, 182, 228, 27, 87, 86, 51, 143, 251, 10, 24, 114, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}