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: 48e844283f68872c66467051b82a12f48a51e1dcfd9c9205bfedd6804693db08
Tx prefix hash: c1f322fc7b25b64e79d93ab95dd9fa112c44dd6e48465cef29485d176d7f6a3d
Tx public key: 0c00e7fb7721b57bae844c3c13b3e40884bb05b325a68889f802e9f99632af71
| Timestamp: 1780017421 | Timestamp [UTC]: 2026-05-29 01:17:01 | Age [y:d:h:m:s]: 00:010:23:29:46 |
| Block: 4125 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3761 | RingCT/type: yes/0 |
| Extra: 010c00e7fb7721b57bae844c3c13b3e40884bb05b325a68889f802e9f99632af7102090000000326697be300 | ||
1 output(s) for total of 34.908700495668 HMNY
| stealth address | amount | amount idx | tag |
| 00: a0370c831316f65ea98088a21d07cb53a5a693c55acb656a200e6aa3ecc70587 | 34.908700495668 | 5148 of 0 | <fc> |
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": 4185,
"vin": [ {
"gen": {
"height": 4125
}
}
],
"vout": [ {
"amount": 34908700495668,
"target": {
"tagged_key": {
"key": "a0370c831316f65ea98088a21d07cb53a5a693c55acb656a200e6aa3ecc70587",
"view_tag": "fc"
}
}
}
],
"extra": [ 1, 12, 0, 231, 251, 119, 33, 181, 123, 174, 132, 76, 60, 19, 179, 228, 8, 132, 187, 5, 179, 37, 166, 136, 137, 248, 2, 233, 249, 150, 50, 175, 113, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}