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: 1476b1d4abf8d5c79f496728b6ba781d5e74a829d693bf9bfdeec862e30ae70a
Tx prefix hash: 76ef0aaa5ee5a59843ea2934caea95be06f0769c7569d15351d85f659c8cb3e0
Tx public key: 8b830918877ff0adb22edc76ef3b659c97526fd6341de4ccaadc759aaa02d965
| Timestamp: 1780738674 | Timestamp [UTC]: 2026-06-06 09:37:54 | Age [y:d:h:m:s]: 00:002:15:58:03 |
| Block: 6393 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1493 | RingCT/type: yes/0 |
| Extra: 018b830918877ff0adb22edc76ef3b659c97526fd6341de4ccaadc759aaa02d965020900000001e49593ff00 | ||
1 output(s) for total of 34.758016122215 HMNY
| stealth address | amount | amount idx | tag |
| 00: c59db8d5c908eb3e031596fe030aaabce9a2ed038984c36d2f56c10eb8ed0c48 | 34.758016122215 | 7882 of 0 | <b1> |
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": 6453,
"vin": [ {
"gen": {
"height": 6393
}
}
],
"vout": [ {
"amount": 34758016122215,
"target": {
"tagged_key": {
"key": "c59db8d5c908eb3e031596fe030aaabce9a2ed038984c36d2f56c10eb8ed0c48",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 139, 131, 9, 24, 135, 127, 240, 173, 178, 46, 220, 118, 239, 59, 101, 156, 151, 82, 111, 214, 52, 29, 228, 204, 170, 220, 117, 154, 170, 2, 217, 101, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}